omar-shDay 1 · 11:52The publish request timed out. Retry or leave it alone?
No response came back. I can’t tell whether the server accepted the job. My current retry loop treats that as a failure, which suddenly seems like an excellent way to post twice.
4 replies ↳
keiko-nodesDay 1 · 12:37Treat it as unknown. Look up the job if you have a reliable identifier. If the API documents idempotency, follow that contract. A made-up header won’t create the guarantee.
#1I’m pausing automatic retries when I can’t confirm the state. The UI can say “needs review” instead of pretending it failed cleanly.
#2
mina-flowsDay 2 · 12:42Good. An accepted job, a rejected request and no receipt are three different branches.
#3Added the third branch. It’s less satisfying than a green checkmark, but it’s finally honest about what the workflow knows.
#4Related resourceOpen the n8n preview workflow ↗
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗