starred/hoppscotch

Fork 0

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

[GH-ISSUE #5528] [bug] Environment variables fully overridden when changing Environment during pending request #2133

New issue

Closed

opened 2026-03-16 23:17:48 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 23:17:48 +03:00

Owner

Originally created by @jakfalter on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5528

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

N/A

Current behavior

Switching Environments during an active request will completely overwrite all (both current and initial) environment variable values with the values from the Environment that has been selected before. This is a critical data loss issue - user data in environments can be accidentally corrupted by switching environments at the wrong time.

Expected Behavior

Environment variable values should never be updated during request execution.

Steps to reproduce

Create two Environments A and B with the same variable test-variable and set it to ABC in Environment A and DEF in Environment B.

Here is how it looks in the Database

Select Environment B.
Now send some kind of request that uses the variable from the environment and does not immediately respond. To test I have sent a simple GET request to koreanbuilds.net as it gave me 5 seconds during which I switched to Environment A.

Now check the contents of Environment A, test-variable is now overwritten with DEF

We can confirm the same by looking into the database

Hoppscotch Version

Server: Self hosted 2025.6.1
Client: MacOS Desktop 2025.6.1

Interceptor

N/A

Browsers Affected

N/A

Operating System

MacOS

Additional Information

N/A

Originally created by @jakfalter on GitHub (Oct 29, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5528 Originally assigned to: @nivedin on GitHub. # Is there an existing issue for this? N/A # Current behavior Switching Environments during an active request will completely overwrite all (both current and initial) environment variable values with the values from the Environment that has been selected before. This is a critical data loss issue - user data in environments can be accidentally corrupted by switching environments at the wrong time. # Expected Behavior Environment variable values should never be updated during request execution. # Steps to reproduce 1. Create two Environments A and B with the same variable `test-variable` and set it to `ABC` in Environment A and `DEF` in Environment B. <img width="833" height="352" alt="Image" src="https://github.com/user-attachments/assets/9fddddec-0499-4d83-9976-44df0a6feaf1" /> <img width="759" height="296" alt="Image" src="https://github.com/user-attachments/assets/2d1a755e-8436-4535-96f7-ded2d881b1b6" /> Here is how it looks in the Database <img width="1297" height="58" alt="Image" src="https://github.com/user-attachments/assets/fe3d44b8-2617-47a5-b21a-025a9c97a150" /> 2. Select Environment B. 3. Now send some kind of request that uses the variable from the environment and does not immediately respond. To test I have sent a simple GET request to koreanbuilds.net as it gave me 5 seconds during which I switched to Environment A. <img width="1370" height="831" alt="Image" src="https://github.com/user-attachments/assets/6fedf466-57ec-4cf8-a264-83dfea5ba7d5" /> Now check the contents of Environment A, `test-variable` is now overwritten with `DEF` <img width="757" height="293" alt="Image" src="https://github.com/user-attachments/assets/2a754c47-3246-48c1-8b3a-cbab416c68a9" /> We can confirm the same by looking into the database <img width="1458" height="73" alt="Image" src="https://github.com/user-attachments/assets/d9cb564c-b96d-47b3-92c8-affdbc51e9fd" /> # Hoppscotch Version Server: Self hosted 2025.6.1 Client: MacOS Desktop 2025.6.1 # Interceptor N/A # Browsers Affected N/A # Operating System MacOS # Additional Information N/A

kerem

2026-03-16 23:17:48 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-16 23:18:04 +03:00

Author

Owner

@kbamponsem commented on GitHub (Oct 30, 2025):

I could also add on this issue that the pw.env.set isn't working anymore.

My particular case:
I call it in a Post-request script to set some envs after my API call and they are not set.

Thanks.

@kbamponsem commented on GitHub (Oct 30, 2025): I could also add on this issue that the `pw.env.set` isn't working anymore. My particular case: I call it in a Post-request script to set some envs after my API call and they are not set. Thanks.

kerem commented

2026-03-16 23:18:09 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Nov 3, 2025):

I could also add on this issue that the pw.env.set isn't working anymore.

My particular case: I call it in a Post-request script to set some envs after my API call and they are not set.

Thanks.

Hi @kbamponsem, could you confirm if this is reproducible in the latest version?

@jamesgeorge007 commented on GitHub (Nov 3, 2025): > I could also add on this issue that the `pw.env.set` isn't working anymore. > > My particular case: I call it in a Post-request script to set some envs after my API call and they are not set. > > Thanks. Hi @kbamponsem, could you confirm if this is reproducible in the latest version?

kerem commented

2026-03-16 23:18:15 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Nov 13, 2025):

Closing since this is fixed in the latest release.

@jamesgeorge007 commented on GitHub (Nov 13, 2025): Closing since this is fixed in the [latest release](https://github.com/hoppscotch/hoppscotch/releases/tag/2025.10.1).

kerem referenced this issue

2026-03-17 01:14:23 +03:00

[PR #2133] [CLOSED] chore(deps-dev): bump @nuxtjs/color-mode from 2.1.1 to 3.0.1 #3643