GlossiDocs
Start free
Repeat at scale

Inspect jobs and recover failures

Follow each automation job, see what failed, and get the work done again.

Each source file or model an automation picks up becomes a job. The Jobs list on the automation is the record of what happened.

Enterprise. Automations are available on Enterprise.

Read a job

  1. Open the automation.
  2. In Jobs, choose Processing or Completed.
  3. Open a job to see its Status, Outputs, Started time, any Error, and how many times it was retried.

Completed jobs link to their outputs in the render library.

Automatic retries

Failed jobs retry on their own, up to 3 times, waiting longer each time (from a minute up to an hour). A failed AI edit is retried twice and then skipped, while the other edits and renders carry on.

When a job has used its retries, fix the cause, then run it again. For a Manual or New Models trigger, select Run once. For a folder trigger, a file that already has a job is not queued again, so delete the failed job first and then select Run once, or upload the corrected file as a new file.

FailureCheckThen
File was skippedFile type, size (1 GB at most), and whether it sits in a subfolder a Template Match step handlesMove the file or upload a corrected one.
Connector lost accessThe account and folder permissionsSign in again on the trigger or export step.
Model failed to processThe source fileFix the file and upload it again.
Render failedThe template and its shots and clipsFix the template, then Run once.
AI edit failedThe prompt and stylesChange the step, then Run once.
Export failedThe destination folder and accessRestore access, then Run once.

Stop or clean up

  • Cancel in the header stops all of the automation's active jobs. Files that already finished stay where they are.
  • Select jobs in the list to delete them. This also deletes the models and projects those jobs created.
  • Deleting the automation offers Also delete models and projects created by this automation. Renders are kept either way.
  • Pause the automation with the switch in the header to stop new jobs starting.

Duplicate work

Glossi doesn't queue a file that already has a job in the same automation. For API-driven work, send an Idempotency-Key header on writes so a retried request returns the original result. If you consume webhooks, expect duplicates and check the current state through the API. See Webhooks.

On this page