The History page shows every render job your account has submitted — from Studio sends, API calls, Zapier automations, and manual exports — along with live status, duration, and webhook delivery. Use it to track batches as they process, spot failures, and jump straight to your billing page.
Opening History
Click History in the top navigation bar. The page has two tabs: Renders (the job list covered below) and Edit Times (active editing time per design — useful for studio managers; covered in its own section).
The KPI summary row
Four summary cards appear at the top of the Renders tab:
- Today — number of renders submitted today.
- This month — running total for the current calendar month.
- In progress — renders that are currently queued or processing. The count turns amber when jobs are waiting.
- Failed (month) — renders that failed this month. The count turns red if any failures exist — a quick signal that something needs attention.
Filtering the job list
Use the two dropdowns above the table to narrow the list:
- Status — filter to All statuses, Queued, Processing, Complete, or Failed.
- Time range — filter to All time, Today, Last 7 days, or Last 30 days.
When either filter is active, a Clear filters button appears to reset both at once. Changing a filter resets pagination to page 1.
Reading the job table
Each row is one render job. The columns are:
| Column | What it shows |
|---|---|
| Design | The design name (and its Studio folder, if it has one — shown as Folder / Design name). For jobs tied to a Studio design, the whole row is clickable — click it to open that design in Studio. API and Zapier renders without a Studio design show the template name instead and are not clickable. |
| Status | Queued (waiting to start), Processing (running now), Complete (finished), or Failed. |
| Duration | How long the render took once it started. Shown in milliseconds for fast jobs, seconds for longer ones. A dash means the job hasn't completed yet. |
| Webhook | Delivery status for the job's outbound webhook: Delivered, Pending, Failed, or n/a if no webhook was configured. |
| Output | A View link to the finished image for completed jobs. |
| Created | When the job was submitted. |
Pagination
The table loads 50 jobs per page by default (the API supports up to 200 per page for programmatic access). Use the Previous and Next buttons at the bottom to page through results. The count above the table — for example, 1–50 of 342 — updates as you navigate.
Refreshing while a batch drains
The page does not auto-refresh. While a batch of renders is in progress, click Refresh (top right of the page) to pull the latest job statuses and update the KPI cards. The In progress card is the easiest way to confirm when a batch has fully drained.
Where API and Zapier renders appear
History covers your entire account — not just Studio sends. Renders submitted via the API, a Zapier automation, or any other integration appear in the same table alongside Studio exports. If the render was tied to a Studio design, the design name and folder are shown; otherwise the template name appears instead.
Billing link
The Billing button at the top right of the History page takes you directly to your billing page, where you can see your current balance, recent charges, and auto-refill settings. Renders that appear as Complete here are the ones that count against your balance.
Edit Times tab
The Edit Times tab shows how long each design was actively edited — measured in 30-second windows of real activity — from creation (or first human edit, for API-created designs) through the first send or editor close. It is visible to all org members, not just admins.
Two sub-tables appear:
- By editor — median and average active time per team member, with a count of designs and a separate outlier count (designs that exceeded the selected time cap).
- By design — one row per design, sortable by time spent, design name, editor, or end date. Designs created before activity tracking was introduced show a wall-clock estimate labelled est.
Use the time range selector (Last 7 / 30 / 90 / 365 days) and the outlier cap selector to focus on the period and range you care about. Outlier-capped designs are dimmed in the table and excluded from per-editor averages and medians.
Comments
0 comments
Article is closed for comments.