[CoE Starter Kit - BUG] Throttling limits - block so many concurrent object inventory flows from occurring with delays

[devvelegandla]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

We havebeen getting throttling issues for a long time.

Based on recent conversation with Microsoft team here, we enabled the Concurrency Control at flow trigger for below flows and seems working without throttle issues.

Is this something you could add it to the next release?

Thanks,
Devendra

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.23

What app or flow are you having the issue with?

Admin | Sync Template v4 (Solutions)

What method are you using to get inventory and telemetry?

Data Export

Steps To Reproduce

No response

Anything else?

No response

AB#2517

[Jenefer-Monroe]

Hello. Thanks for posting. That setting is one we cannot use as its not reversable and has some other side effects.
But we could add another Delay variable which causes the run from these to start at various times.
Can consider for the April release.

[bch920]

@Jenefer-Monroe what would the other side effects be ? As this has seemed to help us a lot we might look to keep adding it back as unmanaged unless there is a downstream issue we are missing ?

[Jenefer-Monroe]

I dont recall the issues we saw as we tested this long ago but I do know the setting is not reversable and so we are unlikely to introduce as a result.

My suggested feature to mimic would have the same impact. I would add a new env var for delay of these flows and then when you set it to true each of these iterations would delay a random amount of time. So you would end up effectively limiting the number of iterations running at a time.

[Jenefer-Monroe]

Adding this section in the top of the object flows

Driven by this env var.

So you can set this value to Yes (Default is no) and turn the flows you listed above off and back on to ensure you get the needed delay. This will simulate the setting you suggested without the danger of it being something we cant undo.