Unleash client stops fetching #615
Assignees
Labels
Comments
olehfitsyk
changed the title
|
Issue seems to have been introduced with #537 I think it would make sense to extend the retry logic to also cover 404 errors |
HenrikBacher
added a commit
to HenrikBacher/unleash-client-node
that referenced
this issue
May 22, 2024
chriswk
pushed a commit
that referenced
this issue
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We encountered an issue with Unleash Proxy a few times when it seemed that it stopped getting any updates from Unleash. It was caused by the update in unleash-client release 5.2 because it stops fetching Unleash configuration when it encounters status codes 401, 403 or 404. Please see
handleErrorCasesfunction. I agree that it seems like a configuration issue, but in my opinion, after the successful initial fetch, it doesn't make sense to just stop pulling updates from Unleash in case a single 404 is encountered.Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response
The text was updated successfully, but these errors were encountered: