[GH-ISSUE #5927] Variables Do Not Persist After System Reboot in Hoppscotch Desktop v26.2.0 (Logged-in User) #2326

New issue

Open

opened 2026-03-16 23:58:20 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 23:58:20 +03:00

Owner

Originally created by @gzx19990101 on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5927

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

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

Platform

Desktop App

Browser

Chrome

Operating System

Windows

Bug Description

Software Name: Hoppscotch

Version: V26.2.0

Environment: Desktop application (logged in with Hoppscotch account)

Summary:

Variables configured in requests do not persist after a system reboot. Although they work correctly immediately after being set, once the computer restarts, the variables no longer resolve — placeholders appear in the request instead of the actual substituted values.

Steps to Reproduce:

Launch Hoppscotch desktop application (V26.2.0).

Create or edit a request containing dynamic variables (e.g., {{variableName}}).

Set the variable value via the environment or pre-request configuration.

Send the request — confirm that the variables resolve correctly and the actual values appear in the request.

Restart the computer.

Open Hoppscotch again, log in, and send the same request.

Observed Result:

After reboot, the request sends successfully, but the variable placeholders ({{variableName}}) remain unresolved in the final request message. The variables do not take effect, even though the user is still logged into the Hoppscotch account.

Expected Result:

Variables should retain their assigned values and resolve correctly in requests even after a system reboot, given that the user remains logged into their Hoppscotch account.

Additional Notes:

This issue affects both new and previously saved requests.

The scripting method (console.log(hopp.request)) confirms that unresolved placeholders are present post-reboot.

No manual changes were made to variable configurations between login sessions.

Impact:

This bug prevents reliable use of dynamic variables in automated or repeated testing workflows, especially where system restarts occur.

Attachments:

Script file used for debugging

Screenshot showing unresolved variables after reboot

IMTS.json

工单.json

Deployment Type

Self-hosted (on-prem deployment)

Version

Desktop App: V26.2.0

Originally created by @gzx19990101 on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5927 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Desktop App ### Browser Chrome ### Operating System Windows ### Bug Description Software Name: Hoppscotch Version: V26.2.0 Environment: Desktop application (logged in with Hoppscotch account) Summary: Variables configured in requests do not persist after a system reboot. Although they work correctly immediately after being set, once the computer restarts, the variables no longer resolve — placeholders appear in the request instead of the actual substituted values. Steps to Reproduce: Launch Hoppscotch desktop application (V26.2.0). Log in to a Hoppscotch account. Create or edit a request containing dynamic variables (e.g., {{variableName}}). Set the variable value via the environment or pre-request configuration. Send the request — confirm that the variables resolve correctly and the actual values appear in the request. Restart the computer. Open Hoppscotch again, log in, and send the same request. Observed Result: After reboot, the request sends successfully, but the variable placeholders ({{variableName}}) remain unresolved in the final request message. The variables do not take effect, even though the user is still logged into the Hoppscotch account. Expected Result: Variables should retain their assigned values and resolve correctly in requests even after a system reboot, given that the user remains logged into their Hoppscotch account. Additional Notes: This issue affects both new and previously saved requests. The scripting method (console.log(hopp.request)) confirms that unresolved placeholders are present post-reboot. No manual changes were made to variable configurations between login sessions. Impact: This bug prevents reliable use of dynamic variables in automated or repeated testing workflows, especially where system restarts occur. Attachments: Script file used for debugging Screenshot showing unresolved variables after reboot [IMTS.json](https://github.com/user-attachments/files/25707879/IMTS.json) [工单.json](https://github.com/user-attachments/files/25707882/default.json) <img width="2879" height="1799" alt="Image" src="https://github.com/user-attachments/assets/bf7e32eb-4f9c-44b9-80f2-07886a0936a2" /> <img width="2874" height="1771" alt="Image" src="https://github.com/user-attachments/assets/1d1f9c3f-6191-44fb-8fc6-45a2a9e541b1" /> ### Deployment Type Self-hosted (on-prem deployment) ### Version Desktop App: V26.2.0