mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5537] [bug]: Cannot import large Postman collections #2132
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#2132
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 @aperrad on GitHub (Oct 30, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5537
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Windows
Bug Description
What happened ?
I cannot upload large collection from Postman, they disappear.
Scenario
Notion API.postman_collection.json
Logs
This error logs are displayed in browser console
Deployment Type
Hoppscotch Cloud
Version
2025.9.2
@Saket-Entujn commented on GitHub (Feb 20, 2026):
I'm also facing this issue when using the desktop client for Hoppscotch. When I import collections exported from Postman into Hoppscotch, the import message says the process was successful. The collections appear in the Hoppscotch workspace, and I can momentarily see the requests along with the custom variables used in them. However, after refreshing the desktop application, they disappear. This issue is observed whether or not the collections include post-response scripts. I tried using the Docker-hosted version of Hoppscotch, and this issue is not observed there. Based on my experience, this problem appears to be specific to the desktop client application. I have not tried the web version.