Choose the application
Customer Advanced → Cron Jobs and the application workspace open managed application schedules. The account needs its scheduled-tasks feature, an eligible application and current local permissions. These schedules do not grant Linux root cron or arbitrary server command execution.
Schedule fields
Choose the application, a task name, a five-field schedule expression, an installed IANA timezone, relative script/entry point, arguments one per line, supported overlap policy, timeout in seconds and email-notification choice. Review the form's actual runtime constraints. Use a timezone deliberately around daylight-saving changes; the saved IANA zone and server scheduler are authoritative.
Create with POST /v1/applications/{id}/schedules. Existing schedules use /{schedule_id}/update, /delete or /run. Read current schedules before changing them and retain the returned durable operation. A saved expression or manually queued run does not establish that the script executed successfully.
Test execution
Start a harmless task manually through the supported Run action. Follow operation history and inspect application logs, exit status and intended outputs. Confirm the next planned schedule and that overlap policy behaves correctly under a long-running test. If notification is selected, verify configured SMTP and actual recipient receipt separately.
Failure handling
For an unknown entry point, correct the account-relative script and runtime; do not use absolute private server paths. For a timeout, inspect whether the process and its external effects completed before rerunning. Keep task name, application ID, scheduled time and sanitized correlation reference for diagnosis. A missing capability or disabled feature remains unavailable.
Separate server cron controls
EPAdmin Cron Services is part of protected service inspection/control and has different server-management authorization. A Customer scheduled task cannot edit systemd units or root crontabs. The product does not offer a general browser terminal or arbitrary privileged command endpoint. Backup schedules use their own backup-policy workflow and are not interchangeable with application cron.