starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #5718] [bug]: Hoppscotch saving new request to existing request, old api getting updated or removed #2226

New issue

Open

opened 2026-03-16 23:37:51 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 23:37:51 +03:00

Owner

Originally created by @akramrana on GitHub (Dec 22, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5718

Is there an existing issue for this?

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

Platform

Web App

Browser

Chrome

Operating System

Windows

Bug Description

🐛 New request saves into an old request / bottom request disappears

Description

When I create a completely new request in Hoppscotch and save it, it sometimes gets saved into an existing (older) request instead of creating a new entry. In other cases, the last/bottom request appears to get deleted (or replaced) after saving.

This causes loss of previously saved requests and makes collections unreliable.

Steps to Reproduce (observed)

Open Hoppscotch and go to Collections / saved requests
Create a new request (not intentionally editing an existing one)
Set URL / headers / body
Click Save (or Save as new)
Observe one of the following:
- The newly created request overwrites an old one
- The last/bottom request disappears or gets replaced

Expected Behavior

Saving a new request should always create a new unique entry
Existing requests should never change unless I explicitly update them
No request should disappear from the list after saving

Actual Behavior

New request data is saved into an old request
The bottom/last request sometimes disappears or looks deleted (possibly overwritten / moved)

Frequency

Intermittent, but happens often enough to be a major issue.

Environment

Platform: Web (hoppscotch.io)
Browser: Chromium-based (Chrome / Edge)
Workspace: Logged in (if relevant)
Storage: Default browser storage (localStorage / IndexedDB)

Additional Notes / Suspicions

Might be a state binding or autosave race condition
- The editor may still be attached to an existing request ID
- Autosave might trigger before "Save as new" assigns a new ID
The “bottom request deleted” might actually be overwrite/sort/sync, but from user POV it appears deleted.

Impact

High – requests get overwritten / disappear, causing loss of work.

Possible Improvements

Ensure "New request" starts with a fresh unique ID before any autosave
Ensure "Save as new" never updates an existing request ID
Add an overwrite confirmation if an existing entry is about to be replaced
Consider versioning / undo for saved requests

Thanks 🙏

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @akramrana on GitHub (Dec 22, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5718 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System Windows ### Bug Description ## 🐛 New request saves into an old request / bottom request disappears ### Description When I create a **completely new request** in Hoppscotch and save it, it sometimes gets saved into an **existing (older) request** instead of creating a new entry. In other cases, the **last/bottom request appears to get deleted** (or replaced) after saving. This causes loss of previously saved requests and makes collections unreliable. --- ### Steps to Reproduce (observed) 1. Open Hoppscotch and go to Collections / saved requests 2. Create a **new request** (not intentionally editing an existing one) 3. Set URL / headers / body 4. Click **Save** (or **Save as new**) 5. Observe one of the following: - The newly created request overwrites an old one - The last/bottom request disappears or gets replaced --- ### Expected Behavior - Saving a new request should always create a **new unique entry** - Existing requests should never change unless I explicitly update them - No request should disappear from the list after saving --- ### Actual Behavior - New request data is saved into an **old request** - The **bottom/last** request sometimes disappears or looks deleted (possibly overwritten / moved) --- ### Frequency Intermittent, but happens often enough to be a major issue. --- ### Environment - Platform: Web (hoppscotch.io) - Browser: Chromium-based (Chrome / Edge) - Workspace: Logged in (if relevant) - Storage: Default browser storage (localStorage / IndexedDB) --- ### Additional Notes / Suspicions - Might be a **state binding or autosave race condition** - The editor may still be attached to an existing request ID - Autosave might trigger before "Save as new" assigns a new ID - The “bottom request deleted” might actually be overwrite/sort/sync, but from user POV it appears deleted. --- ### Impact High – requests get overwritten / disappear, causing loss of work. --- ### Possible Improvements - Ensure "New request" starts with a fresh unique ID before any autosave - Ensure "Save as new" never updates an existing request ID - Add an overwrite confirmation if an existing entry is about to be replaced - Consider versioning / undo for saved requests Thanks 🙏 ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem added the

bug

need testing

labels

2026-03-16 23:37:51 +03:00

kerem commented

2026-03-16 23:38:02 +03:00

Author

Owner

@akramrana commented on GitHub (Dec 22, 2025):

Also published document not getting updated after adding/saving request.

@akramrana commented on GitHub (Dec 22, 2025): Also published document not getting updated after adding/saving request.

kerem referenced this issue

2026-03-17 01:16:18 +03:00

[PR #2226] [CLOSED] Refactor/websocket system revamp #3679