This repository has been archived by the owner on Aug 27, 2024. It is now read-only.
Display error messages when check execution errored #501
Labels
Comments
prayerslayer
changed the title
6 tasks
fokusferit
pushed a commit
that referenced
this issue
Feb 13, 2019
fokusferit
pushed a commit
that referenced
this issue
Feb 13, 2019
fokusferit
pushed a commit
that referenced
this issue
Feb 27, 2019
fokusferit
pushed a commit
that referenced
this issue
Feb 27, 2019
fokusferit
pushed a commit
that referenced
this issue
Mar 6, 2019
fokusferit
pushed a commit
that referenced
this issue
Apr 3, 2019
fokusferit
added a commit
that referenced
this issue
Apr 3, 2019
* GH-501 adding refresh token functionality to handle edge case of outdated access token * GH-501 adding user name update * GH-501 providing the correct where query and update username * GH-501 adding some better UX to the Refresh Token success flow * GH-501 remove unused code * GH-501 fixing a crazy weird case when refreshing tokens and before hooks are not triggered * GH-501 adding migration scripts for PR check files
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes it happens that a stored token becomes invalid. Zappr cannot update the check status with an error message (because the token is invalid). As we already store whether or not there was an exception during last check execution for monitoring, we could use this information together with the error message to notify users that they should exchange the stored token.
The text was updated successfully, but these errors were encountered: