Draft
Conversation
Co-authored-by: dvir001 <39403717+dvir001@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix code scanning alert #13
Sanitize user-visible employee sync failures
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Alert #13 flagged that raw exception text from employee sync failures could be persisted in sync status and surfaced through the settings API/UI. This change limits externally visible failure details to safe messages while preserving server-side diagnostics.
What changed
str(exc)values in employee sync failure handling with a fixed generic message for unexpected errors.Behavioral adjustment
"No employees returned from Graph API."status as a safe, intentional user-facing failure case instead of routing it through generic exception handling.Tests