Back to Changelog
External API
v1.0.14
Fixed external API cron jobs to run through the same scheduler and isolation engine as the panel.
Bug Fixes
3- Cron jobs created via the external API previously wrote directly to the database, so next_run was never computed and the job was never registered in the scheduler queue, meaning new cron jobs silently never ran until an unrelated scheduler restart backfill picked them up.
- Cron job updates and deletes are now synced to the scheduler queue instead of only updating the database, preventing stale or ghost scheduler entries.
- Cron job creation now enforces the plan cron job limit and ownership checks, which were previously bypassed on the external API.
Security Fix
1- Manually running a cron job via the external API previously executed the raw shell command in-process as root with no user isolation; it now runs through the same sandboxed executor as the panel, as the unprivileged domain-owner user inside namespace and cgroup isolation.