Bånderapp:scheduler:delete
Delete a scheduled job. The command does what Delete on the admin Scheduler page and DELETE /api/admin/scheduler/jobs/{id} do.
Quick start
make exec cmd="php bin/console app:scheduler:delete aB3dE5fG7hJ9kL1mN3pQr --force"
In a script that reads only the exit code:
make exec cmd="php bin/console app:scheduler:delete aB3dE5fG7hJ9kL1mN3pQr --force --json"
Arguments
| Argument | Required | Description |
|---|---|---|
id |
Yes | Public ID of the scheduled job, as app:scheduler:list prints it |
Options
| Option | Description |
|---|---|
--force |
Delete without asking; required when no terminal is attached |
--json |
Print nothing on success, as the admin API answers 204 No Content; the exit code reports the outcome |
Details
Deletion cannot be undone. On a terminal the command names the job and asks before deleting it. Without a terminal, as in scripts and make exec runs without a TTY, it refuses unless --force is given. To stop a job without losing its definition, use app:scheduler:disable instead.
If the job changed while it was being deleted, the delete is refused with Scheduled job changed. Reload it and try again., the conflict the API reports as 409.
With --json the command prints nothing on success, because the API answers 204 No Content; read the outcome from the exit code. Errors still go to stderr. --json does not stand in for --force.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Job deleted |
| 1 | No scheduled job has this public ID, the operator declined, or the job changed concurrently; the message says why |
| 2 | The argument is not a public ID, or no terminal is attached and --force was not given |