Custom app trigger returns data in test but doesn't trigger Zap

Hi ​@automation_journey 

Search the Zapier Developer Platform help center: https://docs.zapier.com/integrations/quickstart/get-help

See section related to Troubleshooting: https://docs.zapier.com/integrations/build/troubleshoot-trigger-timeouts

This behavior typically happens when a polling trigger fails Zapier’s internal deduplication (dedup) check or when there is a missing primary key field. When you test a custom app trigger within the developer console, Zapier displays the raw JSON payload regardless of structure. However, in a live environment, Zapier's engine checks for a unique identifier field (usually named id). If your API output changed around June 12th—such as wrapping the data in a new nested object, changing the id key casing, or returning an empty identifier—the live Zapier polling system will fail to recognize the records as "new" or fail to track them entirely. Verify your code output structure to ensure a clear, unique, and consistent string/integer id field is present on every object root. 

Another common cause is an issue with reverse chronological sorting or a broken pagination loop. Live Zaps require polling endpoints to return the newest items at the top of the array list. If a backend database update on June 12th inverted your sorting order (putting oldest items first), Zapier’s live polling engine assumes no new data has arrived because it only evaluates the top entries. Additionally, double-check your custom app integration settings to confirm your authorization tokens are passing correctly in the live environment. Sometimes, older developer testing sessions rely on cached developer platform credentials that bypass token expiration, whereas live Zaps will silently fail to poll if the production API requests face silent authentication rejections or strict rate limits.