How to Fix Stuck "Saving Workflow" and Make Urgent Changes to Pipe after Deploying New Version before Redis Issue?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

I deployed a new version of my pipe just before the frontend “Redis” issue. My workflow is now stuck saying “Saving workflow…“. I can’t change code, I can’t rollback version, I can’t deploy a new version.
I need to make urgent changes to my pipe.
Please, help!

2

Hi Tim, could you visit your workflow’s Settings and share it with Pipedream support? Then just share the workflow’s URL here if you don’t mind. any chance you can help take a look when you get in?

3

I’d send you a link to DM if you don’t mind

4

Definitely, please share with

5

Done

6

Can please confirm that he received my message and working on it? :slightly_smiling_face:

7

Pierce will be online in a few minutes and we’ll get back to you ASAP

8

Thanks!

9

Any updates? :slightly_smiling_face:

10

any updates?

11

Hello thanks for sharing your workflow with support. This issue doesn’t appear to be related to the outage from this morning.

I believe the issue issue is that you’ve hit your account’s workflow limit on your account.

It appears it’s a v1 workflow, which unfortunately was sunsetted back in February 2022 and it hasn’t been updated with the new messaging regarding active workflow limits.

Please try deactivating another workflow and deploying this one, if you’re able to that means this is most likely the cause. You can upgrade your plan to Advanced for unlimited active workflows, but the Basic tier does not allow more than 20 at a time.

12

How many workflows do I have?

13
14

Did I deploy a new workflow so that could be a problem? No, I just deployed an update.

15

Could you please actually take a look at the problem?

16

In v1 workflows, there’s not a differentiation between updating and deploying, which v2 introduced.

17

Could you try deploying a v2 workflow to see if this same issue occurs?

18

The other area to check is making sure you didn’t accidentally archive an active workflow. That would still count it as active.

19

I had similar issue about a year ago, but back then I needed a quick solution so I just copied a working workflow and used a new one.

20

So if I copy the same v1 workflow and launch it it will work (based on my previous experience)