mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5488] [bug]: Collections/environments get lost #2106
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ankurmalhotra07 on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5488
Originally assigned to: @nivedin on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
macOS
Bug Description
We’ve received numerous reports from users that their collections/environments are being deleted intermittently, forcing them to recreate them.
Upon reviewing the GQLClient, it looks like the authExchange implementation is incomplete. Specifically:
As a result, when a JWT expires, the app isn’t able to refresh it properly. We suspect that GraphQL requests then fail silently, causing data to be stored locally. When users log in again, the local storage is cleared, which may explain the data loss.
Is this a known issue? we can look into properly implementing didAuthError and refreshAuth to handle token expiration.
Deployment Type
Self-hosted (on-prem deployment)
Version
No response
@ankurmalhotra07 commented on GitHub (Oct 17, 2025):
@AndrewBastin
@jamesgeorge007 commented on GitHub (Oct 31, 2025):
Hi @ankurmalhotra07, we've included the proposed updates that are now live with the latest release. Please let us know if the issue persists.