Answered

Status 429 error

(0) Share

Report

Posted on by JTull99

Hello,

I am using a flow that will send an email when specific fields in a SharePoint site Issue Log change. Normally, the flow runs successfully. However, in the early afternoon, it starts to fail. I am aware that 429 can equate to too many requests. I have throttled the concurrency control to 1 which did not seem to fix the issue.

Questions:

Is there a way to determine how many requests are too many?

Any suggestions how how to remediate?

Thanks in advance!

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

AnthonyAmador 2,553 Moderator on at

Like (0)

Report
Hi @JTull99

You can check the throttling limits for the SharePoint connector here.
SharePoint - Connectors | Microsoft Docs

You can alleviate the problem by:
Redesigning your flow to use fewer actions and less data.
If you have 'Do until' or 'For each item' loops in your flow, see if you can reduce the number of loop iterations, possibly by retrieving fewer items to iterate through.
Many connectors have 'Filter query' and 'Top count' parameters that can be used to reduce the number of items and amount of data retrieved. Filtering with Odata
If you have a scheduled flow that runs frequently, consider reducing the frequency. Many flows that run once per minute or hour could be revised to occur less often.
If your flow is interacting with files, be conscious of the file size and try to reduce it if possible.
If you need to reuse a single property returned by an action with large output size multiple times, consider using 'Initialize Variable' to store that property, and use the variable in later actions. Even if only one property is used from an output of an earlier action, all outputs of that action that will be passed into the later action as inputs.
Hope this helps.
Kind regards.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
JTull99 6 on at

Like (0)

Report

@AnthonyAmador,

Thanks for the response.

I have the flow below - not sure if it could be redesigned to have less steps.
The flow does not have any 'Do until' or 'For each item' loops.
I do not think I am using 'Filter query' and 'Top count' parameters.
This is not a scheduled flow.
The file is text - a few names, a title, description (6 lines max), action, etc. Nothing too excessive.
I will investigate "If you need to reuse a single property returned by an action with large output size multiple times, consider using 'Initialize Variable' to store that property, and use the variable in later actions. Even if only one property is used from an output of an earlier action, all outputs of that action that will be passed into the later action as inputs."

The flow is based on an issue log that currently has under 100 items.

It has been experiencing issues between 1:00 PM and 3:00 PM. At that point, flows run for excessive durations, and others queue up. At a later point in the day (off hours) about 95% of the flows complete. Any flow that is still running (run time of several hours) will be canceled and resubmitted. Completion time is < 1 second.
Concurrency Control is on. I have tried this with values between 1 and 10. This can cause some flows to wait, but generally they complete.

The flow in question has these components:
1 - When an item or file is modified This completes without issue
2 - Get changes for an item or file (properties only) This completes without issue
3 - Condition - Has column changed status This is on three fields - Status, Priority, Action Taken
If Yes
Send an email notification (v3) When the 429 occurs, it is at this step

Overall, the flow runs in < 1 second.
Generally, there are less than 3 flows running at the same time.
However, when a flow starts to run long it will impact others and start a bottleneck. A few flows will complete, then things seem to hit a wall.

Thanks

Was this reply helpful? Yes No
Verified answer

AnthonyAmador 2,553 Moderator on at

Like (0)

Report

I think the problem could be in the action "send an email notification". This particular action has very low limits.

Mail - Connectors | Microsoft Docs

Instead, try using the action "send an email (V2)" and let me know if it works better.

Hope this helps.
Kind regards.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
JTull99 6 on at

Like (0)

Report

@AnthonyAmador,

Thanks for the suggestion. I have revised the code and will monitor.

Was this reply helpful? Yes No