This topic was automatically generated from Slack. You can find the original thread here.
Hey folks! Small startup here
I’m working on a workflow that needs to pause and resume via a resumeUrl
— this is part of a system where:
- a Chrome plugin sends initial data to a Pipedream webhook to start the workflow
- I process that data in the workflow with some code which outputs json
- I then need to send back that data to the Chrome plugin
- The chrome plugin performs an operation on that data locally on the system its installed on
- The plugin then sends back the final json payload which is needed in the rest of the workflow so that the workflow can continue processing
To make that work, I need to generate a dynamic URL in the workflow that I can send back to the plugin as aresumeUrl
. I’ve tried multiple approaches:
What I’ve tried:
•$.flow.generateStaticResumeUrl()
Throws
is not a function
•$.workflow.url
and$.context.workflow.url
Returnundefined
during execution
•$.executionId
and manually constructing a URL likehttps://e.pipedream.net/${executionId}
When triggered live via a real request to the deployed webhook, it resolves tohttps://e.pipedream.net/undefined
In all cases, when I try to build the resume URL from these values, I either get errors or invalid URLs when running the workflow live.
What I need:
Before I commit to upgrading to a paid plan, I just want to confirm: Will I be able to reliably generate a valid resumeUrl
(for the current execution) when this workflow is triggered live (not in test mode) if I’m on a paid plan (Basic or Advanced)?
The docs suggest this should work, but my current results suggest otherwise on the free tier. Im now considering buying the 348 dollar plan, but I first want to know if im doing something wrong, or if upgrading will even work at all!
Thanks a ton in advance — I’d love to get this confirmed before I pull the trigger on the upgrade.
With kind regards,
Thijs