Intermittent 400 errors when attempting token refresh
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 205
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
Hi Mautic team,
I'm investigating a customer issue in which we are seeing issues when we attempt to get a refresh_token.
- Net::ReadTimeout with #TCPSocket:(closed)
- refresh_token_request dead: refresh token request 400
This issue seems to come up intermittently, and is impacting our customer's workflows as authentication breaks from time to time, requiring manual re-authorization.
Have you seen these issues in the past, and what is the best way to handle these timeouts and 400 errors when attempting to refresh the access token?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the refresh-token request handling in the PHP API library and trace the timeout and 400-error paths. Done would require a reproducible cause and an agreed fix or documented handling for intermittent refresh failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100