mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3166] [bug]: Saved requests don't appear in collections #1042
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#1042
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 @hungryseashell on GitHub (Jun 30, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3166
Is there an existing issue for this?
Current behavior
When saving a request to a collection, it gets saved but I can't open it as it doesn't get listed in the collection.
When exporting the collection the request is there in the exported file it is only missing from the UI.
In the attached screenshot the bottom 2 collections are opened. The bottom one is correctly displaying as empty, as it doesn't contain any request. The middle one contains a request but it doesn't get listed.
Same behaviour on chromium and firefox. Tried logging in in incognito mode, but got the same behaviour.
Steps to reproduce
Environment
Production
Version
Cloud
@davelet commented on GitHub (Nov 7, 2024):
same on desktop version.
@codingonHP commented on GitHub (Oct 2, 2025):
Works fine on Desktop now - v 2025.9.1
@liyasthomas commented on GitHub (Oct 3, 2025):
We experienced unprecedented backend infrastructure downtime yesterday, briefly affecting Collections and Environments. All systems are now operational and data should be unaffected.
If you still encounter issues, reopen the ticket.