Background jobs
In this sectionRun work outside the request that started it: durable TaskIQ tasks on a worker and scheduler, or fire-and-forget tasks in the graph process.
- 3 pages
- About 18 min to read all
Background jobs cover work that runs outside the request that asked for it. Use in-process tasks for work you can afford to lose on a restart. Use the TaskIQ worker and scheduler for work that must survive a restart, runs on a schedule, or scales separately.
- How jobs work: When to use in-process tasks versus the TaskIQ worker and scheduler, and how identity carries into each run.
- Worker and scheduler: Durable TaskIQ tasks run by the 10xgraph worker and scheduler, started from Python or over HTTP, with schedules, cancel and progress.
- In-process tasks: Fire-and-forget async tasks launched from a node with BackgroundTaskManager, without blocking the response.
All pages in Background jobs
- Background jobsWhen to use in-process background tasks and when to use the TaskIQ worker and scheduler, how tasks are started over HTTP, and how identity carries into each run.2 min
- Run background tasks with a workerDurable tasks on TaskIQ with the 10xgraph worker and scheduler, started from Python or over HTTP, with schedules, cancel and progress.11 min
- Run work in the backgroundLaunch fire-and-forget async tasks from a node without blocking the response using BackgroundTaskManager.5 min