-
Notifications
You must be signed in to change notification settings - Fork 32
Troubleshooting User Errors
asyasky edited this page Jan 23, 2020
·
1 revision
Easy things to check
- Ask them to try in an incognito window (Windows aggressively signs on with the linked corp or MSA for the Windows user even though we have the setting to not do that)
- Ask them to double check that they're signed in with the account they want to be using.
- Make sure that they've given the app permissions to access their profile (this can be checked at https://account.live.com/consent/Manage while signed in to the MSA they want to use)
Matching the error in AppInsights:
- Find out when the error occurred (don't forget to account for timezone) and expand the time filter accordingly.
- If possible, get the RequestID from the error page. Then go to Application Insights -> Search and paste in the second section of the RequestID (00-XXXXXXXXXXXXXX-YYYYYYYYY-00 it's only the XXXXXXX section).
- If the RequestID isn't available look at the Failures tab and see if any exceptions match the symptoms.
- First-time setup
- Contributing using git
- Local Development Environment Setup
- External Authentication Setup
- Build and run locally
- Best practices
- Common Errors
- Making a page Event aware
- Making your page aware of the current user
- PageFilter and on page authorization check example
- Updating the DataModel and or Database Schema
- Debugging the database locally
- FAQ
- Onboarding
- Puzzle setup
- Puzzle properties defined
- Webification
- Unlock a puzzle for a team
- Setting up hints
- Puzzle lockout
- Annotations