cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Kudo Commander
Kudo Commander

There's a problem with the flow's trigger: BadGateway 502

With using the trigger When a file is created or modified - it has worked fine for a day but suddenly existing flows and newly created flows show this error not triggering new runs any more.

Created a very simple totally new Flow to focus on trigger:

MicrosoftFlowTriggerSimple.png

MicrosoftFlowTriggerErrorLibrary.png

When only editing an existing Document Set it runs correctly (see successfull run below of 11 mins ago related to the edit above of 12 mins ago), when adding new Document Set (10mins ago) it starts to give the trigger notification in Flow Studio:

MicrosoftFlowTriggerErrorRuns.png

No new Flow runs are triggered anymore for any type of change (New & Edit see the 4 mins ago).

Details of when trying to Fix the trigger:

MicrosoftFlowTriggerErrorBadGateway.png

1 ACCEPTED SOLUTION

Accepted Solutions

So in a desperate last effort, I recreated a totally new library from scratch with the same (Document Set) Content Types and other settings. Now the flow had no issues triggering on this trigger...

 

The only difference is that the erroring flows were triggered from a library copied with ShareGate from an on-prem environment. I'll inform ShareGate about this. Thanx for checking this out!

View solution in original post

3 REPLIES 3
Kudo Commander
Kudo Commander

So tried the following:

  • Issue started within Chrome and account Django
  • Same tenant within InPrivate session of Edge (to avoid caching issues) and account Django - complete new Flow with same trigger and simple variable initialize as only action ==> same issue on trigger
  • Same tenant within InPrivate session of Edge DEV and other Service account  - complete new Flow with same trigger on another library and simple variable initialize as only action ==> same issue on trigger with different library
  • Other tenant with other account and default Document Set ==> no issue at all (on New and Edit)

 

Hi @Django ,

 

I am afraid I am not able to reproduce a similar error, but I have encountered many problems such as There's a problem with the flow's trigger.

The common reason is that the account used to configure the connection does not match the parameters configured in the field. It may also be a permission issue.

 

Please try the following to see if it can mitigate the issue you have encountered:

  • Click Save as to create a copy of Flow, then turn on Flow and configure where it may need to be configured, and finally see if this copy is available.
  • Alternatively, you could export this Flow as a .zip file and re-import it as a new Flow. After doing the relevant configuration, check if similar problems still exist.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

So in a desperate last effort, I recreated a totally new library from scratch with the same (Document Set) Content Types and other settings. Now the flow had no issues triggering on this trigger...

 

The only difference is that the erroring flows were triggered from a library copied with ShareGate from an on-prem environment. I'll inform ShareGate about this. Thanx for checking this out!

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (8,646)