Skip to main content

​
What is the Jobs page?

Imports, compiles and publishes run in the background, so you can leave the page while they work. Each one is recorded as a job. The Jobs page lists them for your whole account: “Import, refresh, validate, compile and export work across this account.” Open it with the Jobs button on the surveys list, from Survey actions → Survey jobs in a survey’s workspace, or with View jobs at the end of an import. Back to surveys returns to the list. The page shows the newest 200 jobs, newest first. It does not refresh on its own — reload the page to see progress. To watch a compile or publish as it runs, stay in the survey workspace instead, where the header badge updates every couple of seconds (see Validate, compile and publish).

​
Filters

A publish runs as a Compile job (its stage reads publishing), so it is listed under Compile. Once the publish succeeds, a separate Publish row records it; that row, like a Copy row for a Voxworks copy, is listed under All only. With nothing to show: “No jobs match this filter.”

​
Columns

The Status column uses the job’s own wording. The same compile shows as Compiling… or Compile failed in the survey workspace.

​
When a job fails

  • Import — the Result column shows why. A failed import leaves nothing behind: “A partial import never presents itself as a complete version — a failed job leaves no half-built version behind.” Fix the file and import again; see Importing surveys for the error messages.
  • Compile or publish — the clearest error list is on the survey’s Readiness tab, in the Compile card, as (code) · (question key) — (message). See When a compile fails.
A failed publish never changes the live version. Jobs are not retried automatically and cannot be cancelled. To try again, press Compile or Publish again in the survey, which starts a new job. A compile that stops reporting for 15 minutes is marked failed with the code worker_lost and can simply be run again.