Documentation
Runtime
Commands, schedulers, and processes
Use command, scheduler, and process tools to keep recurring and long-running work visible after launch.
Updated Jun 22, 2026
2 min read
What runtime operations do
Commands, scheduled jobs, queue workers, and background processes keep application work visible after launch. They are especially important for Laravel sites, imports, notifications, webhooks, maintenance tasks, and long-running services.
Before adding background work
- Know which command should run and from which working directory.
- Confirm required environment values are present.
- Decide whether the work should be one-off, scheduled, or continuously supervised.
- Make sure the team knows where to check output and status.
Typical workflow
- Use site or server commands for one-off checks.
- Add scheduled jobs for recurring commands.
- Add queue workers or supervised processes for long-running background work.
- Review status near the panel that started the work.
- Inspect logs, activity, and failure context before retrying.
Checks before launch
- Queue connection and worker command are known.
- The scheduler command is configured when the application needs recurring tasks.
- Worker restarts are included in the deployment workflow where needed.
- Failed jobs or command failures are visible to the team.
- Destructive scheduled work has a backup plan.
Common issues
- Queues are forgotten until emails or imports stop working.
- Workers keep running old code assumptions after a deployment.
- Scheduled jobs run from the wrong path.
- The team retries a command without reading its last output.