Fix sync flow throttling: default admin_DelayObjectInventory to "yes" #10795
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sync flows (v3 Flow Action Details, v4 Flows) run 7+ hours instead of 30-120 minutes when the Driver triggers 20+ child flows concurrently. Without delays, concurrent API calls exceed Dataverse limits (6,000 req/5min), causing exponential retry backoff that extends runtime by hours.
Changes
Environment Variable Default
admin_DelayObjectInventory:no→yesDocumentation
TROUBLESHOOTING-FLOW-PERFORMANCE.md: root cause analysis, resolution steps, runtime benchmarksREADME.md: added FAQ entry, updated environment variable tableTechnical Detail
Counterintuitive fix: Adding randomized delays (1-5min) between environment inventories makes flows complete faster by avoiding throttling retries. Without delays, flows hit API limits → retry with exponential backoff (1min → 2min → 4min → 8min...) → cascading delays across all concurrent flows.
Migration Path
Existing installations experiencing this issue:
Expected runtime: 30-90 minutes (v4 Flows), 1-2 hours (v3 Flow Action Details)
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.