Jobs are a generic unit of work processed by a background process in our cloud infrastructure. These background processes are not performed synchronously (blocking other tasks, forcing the user to wait). Rather, they are submitted to a queue and then processed asynchronously (while the user has continued on to another screen). These background workers handle...
- Output builds
- Scene render outputs
- Email notifications
- Deployments
- and other tasks.
The jobs these workers start and complete are visible in the list found at infrastructure > jobs.
Understanding Jobs
- Jobs can depend on other jobs as well, and won't start until those dependecies are satisfied. For example, a PDF Quote Output job that bundles other output documents together will wait for all those other product outputs to complete before it will start.
- Job logs are read-only.
- Job log details are in JSON format, so they are easy to read for both company administrators using the Admin portal, and for outside processes using our REST API to query for the status of jobs. They are typically used for troubleshooting, or for providing information other systems in your company.
Jobs and Logs are different.
While the Jobs list shows work that is performed asynchronously (there may be some time between when they are requested and when they are completed), the Logs list shows work that is performed synchronously (the work completes immediately). The troubleshooting information you're looking for may be listed in the other location.