[GH-ISSUE #5167] [bug]: Collections not persisted when access token expires #1968

New issue

Closed

opened 2026-03-16 22:40:30 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 22:40:30 +03:00

Owner

Originally created by @chhaviG22 on GitHub (Jun 18, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5167

Originally assigned to: @chhaviG22 on GitHub.

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Current behavior

When a user’s access token is expired, creating a collection still returns a 200 OK response from the API. However, the response body contains an "unauthenticated" error.
Since the UI does not surface this error, it appears to the user that the collection has been successfully created.
In reality, the collection is not saved to the database, and when the app is refreshed (and a new access token is generated using the refresh token), the collection disappears without any trace—leading to confusion and potential data loss.

Steps to reproduce

Let the user session idle until the access token expires (refresh token still valid).
Create a new collection in the personal workspace.
Observe that the collection appears in the UI as if it’s saved.
Refresh the app.
The newly created collection is no longer present.

Logs and Screenshots

https://github.com/user-attachments/assets/4ce7e368-b4f6-424a-ad33-e6907c48890b

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Not Applicable - Issue not related to network requests

Browsers Affected

No response

Operating System

None

Additional Information

No response

Originally created by @chhaviG22 on GitHub (Jun 18, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5167 Originally assigned to: @chhaviG22 on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior When a user’s access token is expired, creating a collection still returns a 200 OK response from the API. However, the response body contains an "unauthenticated" error. Since the UI does not surface this error, it appears to the user that the collection has been successfully created. In reality, the collection is not saved to the database, and when the app is refreshed (and a new access token is generated using the refresh token), the collection disappears without any trace—leading to confusion and potential data loss. ### Steps to reproduce 1. Let the user session idle until the access token expires (refresh token still valid). 2. Create a new collection in the personal workspace. 3. Observe that the collection appears in the UI as if it’s saved. 4. Refresh the app. 5. The newly created collection is no longer present. ### Logs and Screenshots https://github.com/user-attachments/assets/4ce7e368-b4f6-424a-ad33-e6907c48890b ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Not Applicable - Issue not related to network requests ### Browsers Affected _No response_ ### Operating System None ### Additional Information _No response_