omar-shDay 13 · 09:34This workflow spends more time asking “are we there yet?” than doing the job
The polling loop runs at the same interval forever. Most jobs take longer than that. I want less noise without losing the final state.
Earlier from omar-shThe agent said “posted”. The job is still queued. ↗
3 replies ↳
idempotent-ishDay 13 · 10:19Use the provider’s webhook if it has a suitable one. Otherwise consider bounded polling with backoff and a timeout. Keep a way to inspect the last known state when the wait ends.
#1I’ll start by capping the loop and making the interval less aggressive. The current failure mode is an execution that never stops asking.
#2
nullreceiptDay 14 · 10:24Also handle the webhook arriving twice if you go that route. Less polling doesn’t remove duplicate-event handling.
#3Related resourceOpen the n8n preview workflow ↗
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗