We’re experiencing an issue with the Wait node’s $execution.resumeUrl where the resume URL when we reach the wait node doesn’t match the resume URL we store in our database, causing approval callbacks to fail.
Our Workflow:
-
Initial Webhook receives quote data
-
Create record in Supabase database with execution_id and resume_url
-
Wait node (Resume: “On Webhook Call”) pauses for approval
-
External webapp calls the resume URL for approval/rejection - but the stored resume_url that goes to Supabase is incrementally different to the one in the wait node when we execute it.
/webhook-waiting/634 (Supabase)
/webhook-waiting/635 (on n8n)
All within the same execution.
When our webapp tries to resume using the stored URL, it fails because the execution context is different.
Has anyone experienced this before or have any advice?
We even tried directly setting the field before we send it to Supabase, but still when it reaches the wait node, the resume URL changes by +1
We have not tried this in production, so if this is a test-webhook specific problem that’d be great to know. Thanks!
- Self-hosted on Hostinger VPS