Skip to Content
Browse documentation

Manage Cron Jobs in UAPP

Review account cron commands, edit schedules, update notification email and confirm job deletion in UAPP.

Open Cron Jobs → Cron Jobs.

Review jobs

The searchable table lists schedules and commands with actions. Use the command copy control where available. The list excludes stored mail/shell metadata; it is a job-definition list rather than execution history.

Do not put passwords, access tokens or other secrets in commands that may appear in the table or clipboard.

Change a schedule

  1. Select the schedule edit action for the job.
  2. Review the existing command.
  3. Choose the new timing with the schedule builder.
  4. Check the updated schedule-and-command preview.
  5. Confirm the schedule change.
  6. Refresh and verify the saved timing.

The dialog rejects submitting an unchanged schedule. The server checks that the selected job exists in the account's definitions.

This action changes the schedule only, not its command. To replace a command through these menus, preserve the old definition, add the intended replacement and deliberately remove the obsolete job, avoiding duplicate execution.

See Add Cron Job for supported schedule syntax.

Notification address

Open the notification-email control, enter a required valid email address and confirm the update. It is an account cron notification address, not a separate address for each job.

The form does not accept an empty address as a disable-mail action. Mail delivery depends on scheduler/mail configuration and the command's output; updating the address is not a delivery test or guarantee of execution notifications.

Delete

Select the job's delete action, review its identity and confirm. Keep its schedule and command if you may need them again.

Deletion removes future scheduling

Deleting a definition does not establish that a command already running was stopped. Check application activity separately before assuming work ended.

Deletion is blocked in demo mode.

Failure handling

Changes are recorded before the crontab rebuild is requested. If a rebuild fails, refresh before retrying because the stored definition may already have changed. Ask the provider to inspect the effective crontab and scheduler rather than repeatedly adding duplicate jobs.

A success message confirms the panel operation, not the command's successful execution.