Issue with Old v1 Flows Reporting: Relation to AWS Error and Possible Resolution?

Help
1

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

Sudden issue with old v1 flows reporting

“Pipedream Internal Error
Please retry your event or reach out to Pipedream support if this error persists.

I am aware that v1 is no longer available for new flows etc. but these are old ones that have not been touched in months and are actively used be several services. Is there anything that can be done to resolve the issue?

Is there any chance it relates to the AWS error mentioned on https://status.pipedream.com/

2

Hi Liam, yes, that’s likely the cause of the issue

3

Getting the same here: Pipedream Internal Error
Please retry your event or reach out to Pipedream support at https://pipedream.com/support/ if this error persists

4

see above

5

Now I am also seeing the problem on 1 of the newer flows as well. I guess we just need to wait this out?

6

Just FYI, it seems issues are all resolved and everything is back to normal. Thank’s for the information.