Jobs
Anything the panel does that takes longer than a page load runs as a job: creating a site, a backup, an update, a command. Each job keeps a log you can read while it runs, and ends as succeeded, failed or canceled.


How jobs run
Section titled “How jobs run”A site has one active job at a time. A second change to a busy site is refused with
409 job_conflict. Each server also runs one job at a time, so jobs for sites on the same server
wait for each other. A site move holds both of its servers.
Some work runs in a lane of its own, beside the server’s other jobs:
| Lane | What runs there | At a time |
|---|---|---|
offsite:<server> |
Offsite copies | One per server |
exec:<server> |
WP-CLI commands, shell commands and REST API requests | One per server |
scan:<server> |
Malware scans and plugin zip checks | One per server |
images:<server> |
Since 0.4.1 A server’s new site images, after a PHP release | One per server |
housekeeping |
The nightly housekeeping | One |
backup-delete |
Since 0.3.0-beta.2 Deleting several backups at once | One |
external-0, external-1 |
Since 0.3.0-beta.3 Every job of a site hosted elsewhere, which runs on no server of the panel | One in each |
A PHP site’s cron lines are not jobs. They run beside the jobs and their lanes, and each line keeps only its last run.
A container app’s deploy hook queues one deploy at a time. A call while one waits is that deploy, which takes the newest image when it starts. A call while the app is busy with another job is deployed once the app is free.
Find a job
Section titled “Find a job”Open Automations → All jobs. Each row shows the job, its site, a summary, its status, who started it and how long it took. The summary masks anything that looks like a password.
- The search box finds
#123as that job. Other text matches a summary, site, error, job type or job name, so “inventory” finds the scans. - The status chips combine, such as Failed and Canceled together.
- Job, Site, Server, Triggered by and When narrow the list further.
The filters are part of the page’s address, so you can bookmark a filtered list or share it.
See who started it
Section titled “See who started it”| Triggered by | Shown as | Means |
|---|---|---|
| In the panel | The admin’s username | Someone clicked something in the panel |
| API | API key "deploy-script" |
A request made with that key |
| AI apps (MCP) | Claude via MCP (approved by sam) or API key "deploy-script" via MCP |
An AI app’s tool call |
| Schedule | The schedule’s name | A schedule fired on its own. Run now is credited to whoever pressed it |
| System | Panel | Follow-up work the panel queued itself |
Follow a job
Section titled “Follow a job”A job’s page shows its Details, What this job does and, once it ends, its Result. The Log follows the job live. Show only Warnings & errors, search it, Copy it or choose Download .log. On a failed job, Show in log jumps to the first error.

Watch the jobs you start
Section titled “Watch the jobs you start”Since 0.3.0-beta.4 A job you start opens the job console in the bottom right corner of the window. It names the job and shows how it stands and its newest log line. It stays while you move to other pages, and a reload keeps it.

- Show log unfolds the log, and Hide log folds it away. Open job opens the job’s page.
- Drag the handle on its left to move it. Your browser remembers the place. Double-click the handle to put it back.
- Minimize sends it to the header, next to the version. It stays there through the jobs you start next, and shows whether they are running or one failed. Choose it there to read the log again.
- Once every job in it has ended and its log is hidden, it shows how they ended for three seconds. Then it goes to the header by itself, and the next job you start brings it back.
- Close appears once nothing in it runs, and clears it.
Several jobs share the console. It keeps the five newest, and a row of buttons switches between them.
Cancel a job
Section titled “Cancel a job”Choose Cancel job. A queued job is canceled at once. A running job stops at its next safe step, once you confirm with Cancel the job. Most jobs keep what they already did. Creating a site and moving one undo their own steps instead.
A WP-CLI command, shell command or REST API request that has started cannot be interrupted. It runs to its end or to its time limit.
Stuck and timed-out jobs
Section titled “Stuck and timed-out jobs”Each job type has a time limit, which GET /api/jobs/types lists. An update that backs the site
up first gets an hour more, the time a backup job has. A job past its limit fails with “Job timed
out after” a number of minutes, and stops at its next safe step.
A job that was running when the panel restarted fails with “Interrupted by panel restart”. A site it was creating or deleting is marked as an error. Run the job again.
Keep finished jobs
Section titled “Keep finished jobs”Finished jobs are kept for 90 days by default. Then the nightly housekeeping removes them with their logs. Change the period under the list, at Finished jobs are kept for.
Limits
Section titled “Limits”- A long job delays the other jobs on its server.
- The job console shows the jobs started in that browser tab. Jobs started by schedules, the API, AI apps, other admins or other tabs are under Automations → All jobs.
- A bulk run shows its progress on Sites → Bulk management. A Run now that starts several jobs lists them under its schedule.
- The job console’s place belongs to the browser, not to your account.
- The panel runs at most eight jobs at the same time, across all servers.
- A job stopped partway, by a cancel or a timeout, can leave its work half done. Its log shows how far it got.
- An interrupted job is not resumed.