Render history and downloads

Renders brings together your project’s PDF jobs so you can find results, inspect submitted data, and follow work in progress. Each job has its own render ID, even when several jobs use the same template and inputs.

1. Find a job in the project

Open Renders and use search and status filters to narrow the list. Opening it from a template may apply a template filter; clear that filter to see the whole project.

Select a row for details. Keep the render ID when discussing a specific error or file, rather than relying on the template name alone.

2. Read job status and errors

Webhook delivery status describes notification delivery separately. Use render status to determine whether PDF generation succeeded.

3. Inspect data and download the PDF

Job details show the template, version, timing, input data, and any error message. Use these to identify the actual edition and inputs used.

Download is available when rendering succeeded and output remains available. File retention depends on the plan; download completed files to your own storage when you need a longer archive.

queued is the acceptance status in the render API’s initial response. The app’s stored jobs use pending while waiting or processing; they do not have a separate persisted queued status.

4. Export history data

Choose Export CSV to retrieve history data using the list’s supported filters. The CSV contains job records; PDFs are downloaded from individual render results.

Export applies the current search, status, and template filters, within a maximum 90-day window. Only records still retained are available; the export does not recover records removed by the plan’s retention policy.

Use CSV for reconciliation, reporting, or lookup outside the app. See plan limits for quota and output retention.