Is Deploying a New Version of an Existing V1 Workflow Still Possible or Are They Now Deprecated?

1

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

Good morning everyone! Is deploying a new version of an existing v1 workflow still possible or are they totally deprecated now?

2

Hi John, no v1 workflows are still deployable. They’re deprecated but should still be functional.

Could you double check and make sure you’re not hitting an active workflow limit? Basic and Free plans are limited to the number of active workflows.

3

The Active Resources section shows I have 29/42 Workflows.

4

The “Deploy” button is blue and clickable. Clicking it just shows “Deploying workflow…” for a moment before changing back.

5

Hm that is strange. Could you share the link to that specific workflow? The ID in the URL would help us look up logs. It should look like p_************

6

Certainly! Does this work?: https://pipedream.com/@diesel-laptops/financing-receive-caleb-parker-response-p_pWCQo2v/

7

p_pWCQo2v

8

Yes, thank you

9

Does this workflow use a data store?

10

Never mind, v1 workflows can’t use data stores. Bad question.

11

All good. I just tried to add an End step to the end of another v1 workflow and it’s doing the same thing, so don’t think it’s that particular flow.

12

I believe it might be an issue with the account connected to one of these steps that’s private.

13

It might need shared with the entire workspace in order to deploy

14

You can change an account’s permission scopes by opening the Accounts page in the dashboard, and then using the menu on the far right to change the access and allow it to be used by the whole workspace.

15

The Accounts used there already show “Workspace” in the Access column there. However when I click on that, it tells me I need to upgrade to manage access.

16

My plan is one of the retired Basic plans that’s no longer available. Is that what’s causing the trouble?

17

I’m seeing other private accounts connected to your workspace, even though they are not part of this workflow they might be the cause. I’ve reached out to our Eng team to find out if that might be the case.

18

All but one of those private accounts aren’t connected to any active workflows, so I can try removing them.

19

Thanks, that might be worth a try

20

I don’t believe that feature should be available for Basic accounts, it might be a legacy subscription issue