This topic was automatically generated from Slack. You can find the original thread here.
I’m trying to find a simple way to pause/disable a workflow running on a trigger. When I go to settings, I see that it’s read-only, so I clicked edit and unchecked “Enable this workflow” in settings, then I “Merge to production” but the read-only settings still shows “Enable this workflow” is checked
I’ve also tried editing the workflow and disabling the trigger, then clicking “Merge to production”, but I still see the enabled trigger in the production branch
It’s v2 and @U02A06JPKEH it still happens if I refresh. I just tried again (both disabling the trigger and disabling the workflow, then “Merge to production” and refresh). I see the change when I hit edit, but not when I’m in the production branch
I tried doing the manual merge via a PR on GH and got this, but I think it works now (I had no idea I had to go to the project to disable/enable a workflow, it’s very counterintuitive)
Also, I think there’s another bug. I reenabled the workflow and manually triggered it and it appears as a successful run on the event log but there’s a 403 error in the workflow
Also, I think there’s another bug. I reenabled the workflow and manually triggered it and it appears as a successful run on the event log but there’s a 403 error in the workflow
I see, thanks. That is likely a bug that we can look into.
can you clarify?
I meant that I had to edit a project to see a “Pause” button on its workflows. I would expect the “pause” button to be in the workflow view, but it’s actually in Edit > Settings > uncheck “Enable workflow”
That is likely a bug that we can look into.
I don’t know if it’s related, but the 403 comes from CloudFlare: “Sorry, you have been blocked”. It also gives me a Cloudflare Ray ID: 84ab34425e1307b7 and Pipedream’s IP 3.80.99.12
This started happening on January 23 (no issues before). I contacted Splitwise, but they say it’s a Pipedream issue :man-shrugging: Anything I can try?