The Flows Activity tab (delivery log)

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. Every member of your organization can open the Flows and Activity tabs and replay a delivery — only Connection and Routing stay with owners and admins, because they show the connection URL.

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.

Flows page Activity tab: search and filter toolbar, status strip, and the delivery table with row checkboxes and replay actions

Search and narrow the list

The list always loads within a time window, so it never has to read your whole history at once. Combine the toolbar controls to find what you need:

Search — one box, Search any field, filename, or device — or field:value. Type anything and it matches, ignoring case, anywhere inside every field the photo carried, plus the filename and the device name — so field finds Fieldstone School. Press / anywhere on the tab to jump into the box. The search applies as you pause typing, or press Enter to apply it right away. To search one field only, type field:value — for example teamName:mules.
Time window — choose Last 24 hours, Last 7 days, Last 30 days, or Last 90 days. The default is Last 7 days.
Flow — show only the photos a particular flow handled. Leave it on Any flow for all of them.
Photographer — show only the photos one person captured. It appears once your deliveries carry photographers; leave it on Anyone for all of them.
Columns — choose which of your data fields show as columns in the table (see below).
Live — a switch at the top right. Turn it on during an event and the list refreshes itself every few seconds, with a pulsing green dot beside the switch while it's running. The refresh button next to it reloads on demand.

Every filter you apply shows as a removable chip under the toolbar — a search reads Team Name contains mules when it's scoped to a field, or Any field contains mules for a plain term. Click a chip to drop that filter, or Clear all to start over.

The status strip

Above the table, four tiles count the deliveries in your window and double as the status filter: All, Delivered, Needs attention, and Replaying. Click a tile to show only that group; click All to clear it.

Delivered (green) — the photo reached its flow and the run started, or a replay of it succeeded.
Needs attention (red) — anything that isn't known-good and isn't still in flight. It's deliberately open-ended, so a brand-new kind of problem lands here rather than being quietly counted as delivered.
Replaying (blue) — a replay is in progress.

The tiles count each delivery's current state — a no route delivery you replay successfully moves out of Needs attention and into Delivered.

Two statuses read differently than they used to: a delivery that reached its flow now shows as success (it was launched), and one that couldn't start its run shows as run failed (it was launch failed). Only the wording on screen changed — the names used for filtering and in the API are the same as before.

Read the delivery table

Each row is one delivery, newest first. The columns are:

Selection checkbox — for replaying several deliveries at once.
Photo — a thumbnail of the photo that arrived.
Who — who or what the delivery is: the player's name, else the team, else the filename. Photos taken in the Templified Tether app add a second line naming who captured the photo and the device they used — for example Matt on Matt's iPhone. Hover that line to see when the shutter fired.
Status — the delivery's current state, not just what happened when the photo arrived, as a colored pill matching the status strip. Once a replay finishes, the status settles into replayed or replay failed, and a sub-line under the pill keeps the history — for example was "no route" · replayed 39m ago, or simply Replayed 39m ago. Rows whose run didn't finish clean also get a sub-line noting the run's outcome, and a failure shows its error message right under the pill.
Your field columns — up to four of your own data fields, chosen from the Columns menu (for example Team Name, Last Name, Jersey Number). Your choice is remembered for your organization, so the table opens the same way next time.
Flow — the flow that handled the photo.
When — the time the photo arrived. Tether sends the photo's real capture time, so a photo that uploads in a batch or retries over slow venue Wi-Fi still shows the moment the photo was taken, not the moment it finished uploading.
Row actions — hover a row for the open-design and replay buttons at the far right.

Click anywhere on a row to open its details beside the list. You can also walk the rows with the ↑ and ↓ keys, and press Esc to close the panel.

Activity tab: search box with time window, Flow, Photographer and Columns menus, the four-tile status strip, and the delivery table with a details panel open beside it

A delivery row after a replay: green replayed status with a history sub-line reading was no route, replayed 39m ago

Capture details on Tether photos

These details are display-only. When a run fills a photo, the same capturer, device, and capture time are stamped onto the design it produces — they show as a caption under the photo in the editor's layer panel, and as a photo-added entry in the design's history — so anyone opening that design later can see who took the photo. They never change how the photo renders.

A delivery row showing capture details under the Who column: the capturer and the device name

Capture details appear only for signed-in Tether captures. A photo posted by an outside system to your connection URL, or to a flow's own webhook, has no verified person behind it, so those rows show no capture line.

The list is paged. A line under the table shows how many of the window's deliveries are on screen, and when there are more, a Load more button appears beside it — click it to append the next page.

Runs don't get stuck

Occasionally a step finishes its work but its result never makes it back to the run, which would otherwise sit in progress forever. Templified notices this on its own: within a few minutes it checks the step's actual result, and if the work finished, the run picks it up and continues or completes normally. If there's still no result after about an hour, the step fails with stalled: no completion within 60m and the run settles into a final state. A run that settles this way behaves like any other failure — you can replay its delivery from this tab.

Open one delivery's details

Click a row and a details panel opens beside the list, with the stored photo, the delivery's name as the heading, and its status pill. Click the photo to open it full size in a new tab. The arrows at the top of the panel step to the previous and next delivery — as do the ↑ and ↓ keys, so you can walk a whole event without losing your place — and the counter beside them tells you where you are in the list. Close the panel with the × or Esc.

The panel holds:

Timeline — what happened, in order: the photo arriving, which flow it was routed to and which routing rule matched, any failure with its message, a replay, and the run's outcome step by step. If the run produced designs, each one is listed here as a link.
Fields — every data field the photo carried, with its value. Hover a field to copy its value, filter the whole list by it, or promote it to a table column. Empty deliveries read This delivery carried no fields.

Three buttons sit above the timeline:

Replay — re-runs the delivery (see below).
Open flow — jumps to the flow that ran this delivery. It's hidden if that flow has since been deleted, and the timeline then just says the photo was routed to a deleted flow.
Open design — opens the design the run produced, in a new tab.

Open the design a delivery produced

You don't have to open the panel first: hover any row whose run produced something and click the open icon at the far right. If you've replayed the delivery, this 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 a 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.

Replaying a Tether capture keeps its original attribution — the new run stamps the same capturer, device, and capture time onto whatever it produces, so a replay never looks like someone else took the photo.

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, turn on Live or click the refresh button to check where it landed. The details panel has the same action as a full Replay button.

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

Whenever a filter is applied — a search, a status tile, a flow, or a photographer — a Replay all matching button appears at the end of the filter chips. It re-runs the deliveries that match everything on screen, 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, or click Clear all beside the filter chips, 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.