I’ve recently started seeing this after modifying existing workflows with a source as their trigger.
Did something change? What’s the recommended workaround?
1 Like
Yes, the warning is new, but you’ve never been able to issue an HTTP response from a workflow triggered by an event source. We added the warning to make that fact more clear.
$respond() can only be used with the native HTTP API trigger, and will not work with event sources. If the workflow is triggered by a source, and attempts to use $respond(), the HTTP response wouldn’t be issued (technically the event source has already issued the HTTP response).
What source are you using in this case? Can you either:
- Issue the HTTP response from the event source, or
- Convert your workflow to use the HTTP API trigger, instead?
1 Like
That makes sense, then. I created this workflow at the very beginning when I didn’t yet understand how PD worked 