401 Unauthorized -- No tokens available for a user
Opened this issue · 1 comments
hoovercj commented
There is at least 1 user who has authorized the application and the service receives their events in the queue, but there are no tokens stored but the token is no longer valid for the user so the service cannot update their description.
- Recognize this situation and avoid throwing an exception so it doesn't bounce 5 times
- Can I "fix" this somehow? Either via emailing the user asking them to sign in again or something else?
hoovercj commented
404 not found should also be handled. This is returned when the activity doesn't actually exist anymore.