My send/print didn't arrive

This article walks you through the most common reasons a Send To doesn't deliver and how to fix each one, so your renders reach their destination.

Step 1: Check the queue for a "needs attention" or "retry" row

Open the Send To panel in Studio or the editor. Every queued item shows one of three states:

Pending — staged but not yet fired.
Needs attention (amber triangle) — the send can't proceed until you fill in missing information. Click the row to open the relevant prompt.
Retry (red, with a rotate icon) — the send attempted but failed. Click the row to try again immediately.

If the row shows needs attention, the two most common causes are a missing path variable (Dropbox) and missing event codes (partner destinations). Both are covered below.

[Screenshot coming: Send To queue showing one row in 'needs attention' state (amber) and one in 'retry' state (red)]

Step 2: Fix a missing path variable (Dropbox)

Dropbox destinations use a file-path template such as /Renders/{main_event_code}/{team_name}/{design}.jpg. If any token in curly braces isn't set on the design, the row lands in needs attention.

Click the needs attention row. The Fill in missing values dialog opens.
Complete every labeled field — each one corresponds to an unresolved token in the path.
Click Save & continue. Templified saves the values on the design and re-queues the row automatically.
Click Send all (or press Enter) to dispatch the newly-resolved row.

If a field is shown as unfillable, the path template references a text layer that no longer exists on the design (for example, the layer was renamed). To fix it, either update the preset's Dropbox path template to remove the broken reference, or restore the missing layer on the source template and rebuild the design.

Step 3: Fix missing event codes (GFcrew / GFITpro)

GFcrew and GFITpro Auto Print destinations require a Main Event Code and a Destination Event Code to route the send correctly. If either is absent, the row lands in needs attention.

Click the needs attention row. The Add Event Codes dialog opens.
Enter the four-digit Main Event Code (the shoot event, e.g. 1408) and the four-digit Destination Event Code.
Click Save & continue. The codes are saved on the design — you won't be prompted again for subsequent sends of the same design to the same preset.

Auto-deriving the Main Event Code from a folder name

If you organize designs in Studio folders whose names begin with four digits and an underscore — for example 1408_Fall Tournament — Templified automatically extracts those digits as the Main Event Code. A design inside that folder won't trigger the event-code prompt for its Main Event Code. The Destination Event Code must still be set explicitly on the design.

GFITpro location / event code mismatch

If a send reaches GFITpro but the print doesn't appear at the expected station, the station may be polling a different event code or routing code than the one attached to the send.

Confirm that the design's Main Event Code matches the event code GFITpro is polling at that station — or, if your org uses Print Locations (beta), confirm the Prints at: indicator in the Send To panel shows the correct location for this browser.
If you switched locations recently, the per-browser location choice may still point to an old location. Click the location indicator and re-select the correct station.
A design whose location was set when a Print Location was enabled but has since been disabled will fall back to routing by event code. Re-enable the location in Settings → Print Locations or pick a new location in the indicator.

Step 4: Dropbox partial upload

When a Send To preset fans a render out to multiple Dropbox folders simultaneously, Dropbox occasionally rate-limits some writes. Templified retries each upload automatically. If the retry limit is exceeded for one or more copies, the row lands in needs attention with a partial-upload message — some copies arrived and some didn't.

Click the row to see which copies failed. You can then click the row again to re-attempt the failed copies, or wait a few minutes before retrying, since the rate limit is per-folder and resets quickly.

Step 5: Check dispatch status in History

Every send — whether triggered manually in Studio, via the API, or through Zapier — is recorded in the design's History. To view it:

In Studio, hover over the design card and click the History icon, or open the design and click History in the side panel.
Each entry shows the destination, timestamp, and outcome. A failed entry will show an error description that can help pinpoint the cause.

The History view is also useful to confirm that a send you thought was skipped actually ran — API and Zapier sends appear here alongside manual sends.

Step 6: Async sends (the send ran but you didn't see a confirmation)

Some sends — particularly large renders or sends that fan out to several destinations — complete asynchronously. Templified acknowledges the request immediately and finishes the delivery in the background. In the queue, an async row clears once the render and dispatch complete; you may not see an on-screen confirmation if the delivery finished after you closed the panel.

If you're unsure whether the send completed, check the design's History (step 5 above) or look in the destination directly (your Dropbox folder, the GFcrew storefront, or the GFITpro print queue).

Still not arriving?

If none of the steps above resolve it, contact support with the design name, the preset name, and the approximate time you attempted the send. Include a screenshot of the History entry if one exists — it speeds up diagnosis.