Fix invalid access_token error handling in execute.sh#33
Open
Fix invalid access_token error handling in execute.sh#33
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: undefined
This commit fixes issue #22 where the application was failing with: "APIError: Code №5 - User authorization failed: invalid access_token (4)." The execute.sh script now includes TOKEN_INVALID_ERROR_MESSAGE to handle the "User authorization failed: invalid access_token." error message, which was previously not caught by the existing error handlers. This also addresses the "too many requests" bug mentioned in the issue, as the script will now properly regenerate the token instead of continuously failing with the same error. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
konard
changed the title
This reverts commit 5b8b756.
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
1 participant
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.
The script was failing with repeated error messages:
APIError: Code №5 - User authorization failed: invalid access_token (4).The issue occurred because
execute.shwas missing handling for the "User authorization failed: invalid access_token." error message variant. The script only handled other token-related errors (expired, wrong IP, no token), but not this specific invalid token error.Changes Made
TOKEN_INVALID_ERROR_MESSAGEconstant toexecute.shBug Fixes
This also addresses the "too many requests" bug mentioned in the issue. Previously, when the invalid token error occurred, the script would continue making failed requests in a loop. Now it will properly catch the error and regenerate the token, preventing the spam of error messages.
Fixes #22