Background jobs

Read a background job's status

Every background job moves from running to finished and tells you where it is along the way. This page explains what you see in the Background Jobs and Schema Imports tabs.

In the app: Settings › Organization Settings › Background Jobs tab

Job states

State Badge Meaning What to do
Processing or Running Blue The job is working. Watch the progress.
Queued or Enqueued Amber Waiting for a free worker. Usually clears within seconds.
Succeeded or Completed Green Finished without errors. Check the result where the job put it.
Failed Red The job stopped with an error. Read the Message. See Recover from a failed job.

Succeeded and Completed mean the same thing. Different kinds of job use different words.

Schema import states

The Schema Imports tab has a few extra states, because an import handles many objects and can be stopped:

State Meaning
Processing The import is running. The current phase shows next to the badge.
Completed Every object imported.
CompletedWithErrors The import finished, but some objects failed. Open it to fix them.
Cancelled Someone cancelled it. Objects already created stay. You can resume it.
Failed The import stopped with an error.

While it runs, the import’s current phase reads like “Analyzing file structure…”, “Creating 42 tables…”, “Parsing standalone indexes…”, “Parsing foreign key relationships…”, “Creating and analyzing SQL objects…”, or “Applying descriptions…”. The progress column shows objects processed out of the total, with how many succeeded and failed. See Watch import progress.

Progress

The Progress bar is percent complete for the whole job. It’s an estimate: some steps take longer than others, so the bar can sit still while a large item is processed and then jump.

Tip: A bar that hasn’t moved for a few minutes isn’t necessarily stuck. Check Last Updated. If the job hasn’t reported for more than ten minutes, see Troubleshooting a background job.

The Message column

Message is the most useful field when something goes wrong.

  • While a job runs, it says what the job is doing now.
  • When a job fails, it holds the error.
  • Long messages are cut short in the grid. Where a job has its own screen, such as a schema import’s detail page, the full text is there.