The Activity tab on the Flows page is a searchable log of every photo that has arrived at your organization. Use it to confirm a photo came in, see which flow handled it, jump straight to the design a run produced, and re-run any delivery that needs another pass. This tab is visible to organization owners and admins only.
What counts as a delivery
A delivery is one inbound photo. Every time an outside system POSTs a photo to your connection URL — or to a flow's own webhook — that photo is recorded here with its data fields, the flow it was routed to, and the outcome. The Activity tab replaced the older per-flow deliveries panel and is built to stay fast even after your organization has received tens of thousands of photos.
Narrow the list with filters
The list always loads within a time window, so it never has to read your whole history at once. Combine these filters to find what you need:
- Time window — a dropdown at the top left. Choose Last 24 hours, Last 7 days, Last 30 days, or Last 90 days. The default is Last 7 days.
- Status — a row of chips below the toolbar, each showing a count. Click a chip to show only that status; click it again (or the All chip) to clear it. Each chip's dot shows its tone: green for statuses that succeeded, red for those that still need attention, amber for a replay in progress. The chips count each delivery's current state — a no route delivery you replay successfully moves out of the no route chip and into replayed.
- Field value — pick a field name from the selector (it defaults to All fields), then type the value you are looking for and press Enter. The active filter appears as a removable chip; click it to clear. The field selector lists the data-field names your incoming photos have used, so you can search by, for example, a team name or player ID.
Read the delivery table
Each row is one delivery. The columns are:
- When — the time the photo arrived.
- Status — the delivery's current state, not just what happened when the photo arrived. Green means it succeeded, red means it still needs attention, and amber (replaying) means a replay is in progress. Once a replay finishes, the status settles into replayed (green) or replay failed (red), and a sub-line under the status keeps the history — for example was "no route" · replayed 39m ago, or simply Replayed 39m ago. Rows that launched a run but didn't finish clean also get a sub-line noting the run's outcome.
- Routed to — the flow that handled the photo.
- Fields — a preview of the data fields sent with the photo.
The list is paged. When there are more deliveries in the window than fit on the current page, a Load more button appears at the bottom — click it to append the next page.
Open the design a delivery produced
When a delivery has a run that produced a design, its row is clickable. Click anywhere on the row (or the open icon that appears on hover) to open the produced design in a new browser tab. If you've replayed the delivery, the row follows the latest replay's run — you see the newest result, not the original.
- If the run produced a single design, it opens directly in the new tab.
- If the run produced several designs, an Open a design picker appears listing each one by its design name. Click the design you want to open it.
- If the run has not produced anything yet, you'll see No design was produced for this delivery yet.
Replay a delivery
Replaying re-runs the original photo as a brand-new run — useful when you've fixed a flow, updated a template, a run failed downstream, or a photo arrived before its routing was set up. Any delivery that still has a stored photo can be replayed, including no route and unknown flow deliveries — their photo is kept even though they never launched a run. Only an intake that never captured a photo (for example photo fetch failed) cannot be replayed.
Fix the routing, then replay
A no route delivery arrived when no routing rule matched it and no default flow was set. Its photo is safe — fix the routing first, then replay:
- On the Routing tab, add a routing rule that matches the delivery's fields, or set a Default flow.
- Back on the Activity tab, replay the row — or select several rows, or replay everything matching a filter. A replay always routes against your current rules, so the fix takes effect immediately.
If a replay still can't find a flow, it fails with Still no route for this delivery — add a matching routing rule or set a default flow, then replay. In a batch, rows that still have no route are reported as skipped.
Replay one delivery
Hover a replayable row and click the replay icon (labeled Replay this delivery) at the far right. On success you'll see Replayed — a new run is processing, with an Open design button that jumps to the result once the run produces one. The row's status flips to replaying right away and settles into replayed or replay failed on its own once the run finishes; for a long-running flow, use the refresh button in the toolbar to check where it landed.
Replay several at once
- Check the box on each row you want to re-run. Use the header checkbox (Select all replayable deliveries) to select every replayable row on the page.
- A selection bar appears showing how many are selected. Click Replay selected.
A single replay request handles up to 20 deliveries at a time. If you selected more than that, the extras stay checked so you can click Replay selected again to continue.
Replay everything that matches a filter
When a field-value filter is active, a Replay all matching button appears. It re-runs the deliveries that match your current window, status, and field filter — no need to check them individually. This batch is also capped at 20 deliveries per request; if there are more, run it again to work through the rest. Deliveries you've already replayed are skipped, so repeated passes drain the remainder without creating duplicate runs. (Checking rows and clicking Replay selected replays them again deliberately.)
When the list is empty
If a filter combination has no results, you'll see No deliveries match these filters in this window. Widen the time window, clear a status chip, or remove the field filter to see more. If your organization simply hasn't received any photos in the window, the tab tells you so and reminds you that every photo POSTed to your connection URL will appear here.
Comments
0 comments
Please sign in to leave a comment.