Does changing the HTTP Response trigger setting affect the live endpoint before Deploy?

Help
1

Hi,

I need to confirm one specific behaviour before editing a live production workflow.

I have an active HTTP-triggered workflow on Pipedream Free. Its currently deployed HTTP trigger is configured as:

HTTP Response: Return HTTP 200 OK

I want to enter Edit mode and change that trigger setting to:

HTTP Response: Return a custom response from your workflow

Question 1 — most important

Does changing the trigger’s HTTP Response setting remain completely draft / undeployed until I explicitly click Deploy?

In other words, while that change is sitting undeployed in the editor, will the existing live endpoint continue running the currently deployed configuration with Return HTTP 200 OK?

Or can changing this particular trigger setting affect the live endpoint immediately, before deployment?

I’m asking specifically about the HTTP trigger configuration property, not code-step changes.

Why this matters

The currently deployed workflow does not call $.respond() on most execution paths. If changing the trigger to custom-response mode affected the live endpoint immediately before the matching code changes were deployed, live requests could potentially wait for a response that the currently deployed steps never send. So I don’t want to infer behaviour here.

Question 2

If the trigger remains configured as Return HTTP 200 OK, what happens if a code step calls $.respond(…)? Is that call simply ignored/no-op until the trigger is configured for custom responses, or can it throw/fail the workflow?

Question 3 — Free plan

If I enter Edit mode and create undeployed changes on an active workflow, is there currently any supported way on the Free plan to discard those pending changes and return the editor to the currently deployed state without deploying anything? I have seen older community discussions saying there was no discard-changes option, so I’d like to confirm the current behaviour.

I’m deliberately avoiding testing this directly on the production workflow until I know the deployment semantics.

Thanks.

2

Hi @cleancozy01,

Here are detailed answers to your questions about editing HTTP trigger settings in a live Pipedream workflow:

Question 1 — Does changing the HTTP Response setting take effect immediately, or only after Deploy?

Answer:
Changing the HTTP trigger’s HTTP Response setting (e.g., from “Return HTTP 200 OK” to “Return a custom response from your workflow”) is a draft change and will NOT affect the live endpoint until you explicitly click Deploy.

  • While your changes are undeployed in the editor, the currently deployed workflow—including its HTTP trigger settings—remains active and unchanged.
  • The live HTTP endpoint will continue to operate with the “Return HTTP 200 OK” setting until you deploy your changes.
  • No trigger configuration (including HTTP Response mode) is applied to the live workflow until you deploy.

Summary:

You are safe to edit the HTTP Response setting without impacting the live endpoint, as long as you do not deploy.

Question 2 — What happens if you call $.respond() while the trigger is set to “Return HTTP 200 OK”?

Answer:
If the HTTP trigger is set to “Return HTTP 200 OK”, any calls to $.respond() in your workflow are ignored (no-op).

  • The workflow will always return a 200 OK response automatically, regardless of whether you call $.respond().
  • Calling $.respond() does not throw an error or fail the workflow; it is simply ignored until you switch the trigger to “Return a custom response from your workflow” and deploy that change.

Question 3 — Is there a way to discard undeployed changes on the Free plan?

Answer:
Currently, there is no supported way to discard pending, undeployed changes and revert the editor to the deployed state on the Free plan.

  • If you make changes in Edit mode and do not deploy, those changes remain in the editor as a draft.
  • To “discard” changes, you would need to manually revert your edits in the editor to match the deployed version, or refresh the page before making any changes (if you haven’t made any edits yet).
  • There is no “Discard changes” or “Reset to deployed” button as of now.

If you have further questions or need more support, please visit Pipedream

I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double-check my answers and code! Learn how to build your own.