Why is the cloned workflow not saving after replacing the trigger with a new Gmail account and how can it be debugged?

Help
1

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

I cloned a working workflow and replaced the trigger to connect to a new Gmail account, gave all the permissions, and now it’s stuck on “Saving”. I waited several minutes then deleted the source / account and redid the trigger and it’s still stuck on Saving… what do I need to do to debug this? Why is it not saving?

2

Do you see anything relevant in the logs for the source?

3

image.png
image.png383×179 14.6 KB

4

Yes logs look like they are working fine….

5

sorry those are events… hold on

6

image.png
image.png2326×1168 295 KB

7

its just the workflow UI that wont save the trigger

8

Yeah the source looks fine.

9

I started by cloning the workflow, may I just just build one from scratch and copy manually?

10

Worth a shot. :man-shrugging:

11

Hi , I faced similar issue as yours. I’ve notified the Pipedream internal team to check. We’ll update to you asap

12

Thanks I tried doing a whole new workflow and trigger and it doesnt work but my other existing workflow works fine with same trigger on different account

13

It’s like the trigger / source is working fine but it cant be connected to a workflow

14

noted . I’ll also report this behavior to Pipedream team

15

to add existing source to the workflow, on your workflow builder, could you click into the trigger, then select existing?

image.png
image.png2628×1870 417 KB

16

It should allow you to link your existing source to your workflow

17

Yeah its a different source though, I cloned the workflow used for one email address, and then created new source to do similar (but not identical) workflow for another email address.

18

I checked back to see if it’s working now after several hours and same issue even if I delete and recreate the trigger / source. Is it possible that that there’s an issue with having multiple triggers for gmail-new-attachment-received and also multiple for gmail-new-email-received connected to workflows in the same account? any idea what this could be?

19

I now have 6 triggers running every 2 min (2 workflows x 3 mailboxes) on Gmail and I am getting “AxiosError - Request failed with status code 429

"Too many requests, please try again later."

” is this because I am somehow hitting the rate limit on my plan or is the rate limit per workflow

20

And its failing on testing before deployment so not sure if there’s a rate limit on that anyway?