Diagnosing Hoppscotch Environment Variable and Pre‑request Script Failures

Recognizable Condition

When a request sent from Hoppscotch returns an unexpected status code or payload, open the Console tab and you may see messages such as "ReferenceError: variableName is not defined", "SyntaxError: Unexpected token", or a timeout warning. These symptoms indicate that either an environment variable is missing or malformed, or a pre‑request script failed to execute.

Cause and Diagnostic Table

Symptom	Likely Cause	Diagnostic Note
ReferenceError for {{varName}}	Variable not defined in the selected environment	Check the Environments panel for the exact spelling
Wrong value substituted	Variable exists in wrong scope (global vs environment) or duplicated with different values	Compare values in Global and Environment sections
SyntaxError in Console	Pre‑request script contains invalid JavaScript (missing semicolon, unsupported ES6 feature, etc.)	Look for red squiggles in the script editor
Request hangs then times out	Script execution exceeds the configured timeout	Check the timeout setting in Settings → General
Network error with CORS message	Missing or incorrect headers causing browser CORS block	Verify that the request does not rely on Hoppscotch to add CORS headers; the target server must allow the origin

Ordered Checks

1. Open the Environments panel (left sidebar) and confirm that the environment you intend to use is selected. Locate the variable name exactly as it appears in the request (e.g., {{apiKey}}). If the variable is absent or misspelled, note it.
2. Inspect the variable’s current value. Ensure it matches the expected format (string, number, JSON). If the value appears empty or undefined, the variable may not have been saved.
3. Switch to the Pre‑request Script editor for the request. Look for syntax highlighting errors (red underline) or watch the Console tab while editing; a SyntaxError will appear there immediately.
4. With the script open, send the request and observe the Console tab for stack traces. A ReferenceError will show the missing variable name; a TypeError may indicate an attempt to call a non‑existent method.
5. Check the request timeout: Settings → General → Timeout. If the script performs heavy work (loops, large data processing), the default 30 s may be insufficient.
6. Create a temporary environment (click the + icon, name it "tmp‑test"), copy the variable definitions from the problematic environment, and switch to it. Send the request again. If the issue disappears, the original environment file may be corrupted.

Fixes Tied to Findings

1. If a variable is missing or misspelled, add it with the correct name and value in the Environments panel. Use the exact casing that matches the request.
2. If the variable exists only in Global scope but the request expects an environment variable, either move it to the environment (copy the value and delete the global entry) or reference it as {{$globalVar}} if Hoppscotch supports the global prefix.
3. For syntax errors, edit the script to correct missing semicolons, mismatched brackets, or unsupported APIs. Replace any use of require, fs, or XMLHttpRequest with Hoppscotch‑provided alternatives such as pm.sendRequest.
4. If the script is complex, split it into multiple pre‑request steps or move heavy logic to a test script that runs after the response. This reduces execution time and avoids timeout.
5. Increase the timeout setting if the script genuinely needs more time, but keep it under a reasonable limit (e.g., 90 s) to avoid hanging the UI.
6. If the temporary environment resolves the issue, export the original environment as JSON, keep a backup, then re‑import a clean copy or manually correct the erroneous entries.

Escalation Criteria

• The problem persists after recreating the environment, testing with a minimal script (e.g., pm.environment.set('tmp', 'ok')), and confirming that the network request works outside Hoppscotch (using curl or Postman).
• The Console shows internal Hoppscotch errors such as "Uncaught TypeError: Cannot read property 'apply' of undefined" or "Error: Script evaluation failed" that point to the application itself rather than user code.
• You suspect a bug in the Hoppscotch version you are running (check the version number in Settings → About).

When escalating, collect:

• Console output (copy‑paste the relevant stack trace)
• Hoppscotch version and browser name/version
• Operating system details
• A minimal reproducible example (environment JSON, request definition, and pre‑request script)

Submit this information via the Hoppscotch GitHub issue tracker.

Practical Verification Example

1. Create a new environment named "verify‑env". Add a variable testVar with value hello.
2. Create a GET request to https://httpbin.org/anything. In the URL field, use https://httpbin.org/anything?echo={{testVar}}.
3. Open the Pre‑request Script tab and add:

   pm.environment.set('testVar', 'world');
   

4. Send the request. Observe the Console tab; there should be no errors.
5. Inspect the response body. The args object should contain "echo": "world", confirming that the variable was updated before the request executed.
6. Finally, revert the pre‑request script to empty, resend the request, and verify that the echo value returns to hello. This round‑trip validates both variable substitution and script execution.

Limitations and Safety Notes

• Environment variables are stored in the browser’s local storage and are visible to anyone with access to the Hoppscotch instance. Do not store production secrets here.
• Pre‑request scripts run in a sandboxed context; APIs like require, fs, or direct XMLHttpRequest are blocked and will fail silently or trigger security warnings.
• Editing environment variables while a collection is running can cause race conditions where some requests use the old value and others the new value. Pause or stop active collections before making changes.
• The timeout setting applies to the entire request, including script execution. Setting it too low will abort valid scripts; setting it too high may mask performance issues.

Rollback Procedure

1. If you have edited an environment and suspect the change introduced the issue, click the environment’s three‑dot menu and select "Export" to download a JSON backup.
2. To revert, choose "Import" and upload the previously exported JSON file. This restores the exact state before your edits.
3. After import, repeat the verification steps to confirm that the original behavior is restored.