Generated Export Lifecycle
Understand queued, running, completed, failed, expired, regenerated, and downloaded export states.
Article guidance
Many SmartGig exports are generated in the background. That keeps large reports, PDFs, route sheets, and visual exports from blocking the page while they are prepared.
Typical lifecycle
- Requested: A user asks SmartGig to generate a report, invoice, route sheet, running order, site plan, or ticket document.
- Queued: The job waits for the document generator.
- Running: SmartGig builds the file and may show progress messages.
- Completed: The file is ready to download.
- Downloaded or expires later: Download tracking and expiry help keep file access controlled.
What to check before using a file
- Confirm the file belongs to the correct event and module.
- Check the generated time and source status where shown.
- Look for superseded, stale, failed, or expired states before sending the file to someone else.
When to regenerate
- The underlying event data has changed.
- The export failed and you want to try again.
- The generated file expired.
- A module added better output details after the first export.