Why am I not receiving live proofs?

Last Updated: 12/10/2026     Tags: live proof, target, delayed, delay, delivery
  • Switch Version
  • V5
  • V4

If you’re experiencing issues with receiving proof or approval emails, start by checking this documentation on proof issues.

Live proofs have a timeout limit of 5 minutes. When targeting expressions include large recipient pools or complex criteria, delivery delays can occur, or proofs may not be sent at all. To optimize delivery:

  • Use more specific targeting expressions: Narrow down your criteria, for example, by using “random 50” rather than broad targeting terms.
  • Simplify targeting conditions: Avoid intricate or layered expressions. Keeping conditions straightforward reduces processing load, helping proofs reach you faster.
  • Limit data volume: Smaller, simpler recipient pools help prevent timeouts.
  • Activity check requirement: Run an activity check before sending live proofs. If the latest check is missing or stale/out-of-date, live-proof controls are disabled until you run a current check.
  • Access requirement: Nominated live-proof controls require Database.Read access, provided by the Database View role. Users without this access will not see the subscriber-selection controls.

Why can't I find a specific profile in the selector?

Without a search term, the selector shows a sample of checked subscribers across different segment combinations. Use an exact-match lookup by subscriber ID, reference, phone number or email address to find a specific checked subscriber. Search uses a single lookup rather than pagination or a Load more option.

Only subscribers in the audience from the current activity check can be nominated. If a selected subscriber is no longer part of the targeted audience, the live proof cannot be sent until that subscriber is removed or a current check is run.

You can nominate up to 10 subscribers. These subscribers provide the data and personalisation used to generate the proof content; they are not the proof recipients. The proof is sent to the workflow participants selected in the activity.

If you've followed these suggestions but still aren’t receiving proofs, please raise a new support ticket to reach Taguchi Support.