Fix: Deduplicate error logging in orphaned users sync flow #10485
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.
The flow creates an error record for every group where transitive member fetch fails. In environments with 100+ groups lacking proper Graph API permissions, this generates 100+ error emails per run.
Changes
TransitiveErrorLoggedboolean variable to track if error has been logged in current runTransitiveErrorLogged == false, set totrueafter first logFlow Logic
Impact
File:
CLEANUP-AdminSyncTemplatev3OrphanedUsers-B9E28619-A6E0-EE11-904C-0022480B7872.json(+78/-28 lines)Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.