Skip to content

Conversation

@blaine-traudt-hudl
Copy link
Contributor

@blaine-traudt-hudl blaine-traudt-hudl commented Aug 13, 2025

Summary

The error we are getting back when a user's token needs refreshed has a statusCode of -1
Probably a cleaner solution but this is a good enough 🩹 fix for now imo

Investigation

Thanks to @ppoulsen we know that the line failing is this one.
Probably should do some more investigation but I am personally fine with pushing this through but am willing to have push back.

Resources

A picture from my debugging session on the users affected by this:
image

Testing

2 Hudl employees were able to recover their access to the app after this change was put in to effect on a local test build. Now there are no more Graph errors being spammed in the logs 🤷

@blaine-traudt-hudl blaine-traudt-hudl self-assigned this Aug 13, 2025
@blaine-traudt-hudl blaine-traudt-hudl added the bug Something isn't working label Aug 13, 2025
@blaine-traudt-hudl blaine-traudt-hudl marked this pull request as ready for review August 14, 2025 16:42
@blaine-traudt-hudl
Copy link
Contributor Author

Tested and no spamming of internal users. Merging!

@blaine-traudt-hudl blaine-traudt-hudl merged commit 85ab5d1 into master Aug 15, 2025
3 checks passed
@blaine-traudt-hudl blaine-traudt-hudl deleted the AddStatusCode-1ToTriggerRefreshAuth branch August 15, 2025 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants