RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

Troubleshooting

RequestTailor’s most common messages, their cause and what you can do. Texts in italics appear exactly like that in the interface.

Exit codes
0 to 4, for rt send and rt run
Web app
the rt agent companion solves a lot
Help
issues in the core repository or CloudDNA

“The browser blocked this request”

Web app only. The browser allows no request to a server without matching CORS headers and no forbidden headers. RequestTailor then offers to send the request through the companion.

  1. Start rt agent in a terminal.
  2. In the web app, choose Send through companion and, the first time, enter the Pairing code from the terminal.
  3. Send again. The request now goes out natively from your machine.

The same goes for gRPC, WebSocket and SSE: in the web app they always run through the companion. Details and security model: Companion rt agent.

Client certificate: TLS error in the browser

Client certificates work only natively – in the Mac app and with rt. The browser and the companion refuse them with a clear TLS error. For APIs with mTLS, use the Mac app or rt send.

Scripts do not run

SituationCause and fix
Banner “This collection contains scripts. Run them?”, report with a warning noteYou have not trusted the collection yet. Click Trust and run scripts. Not now lasts until the next start.
X is not supported in RequestTailor (…)The script uses an API the shims do not cover. The import’s loss report names it; the list is in SHIM-COVERAGE.md.
Cannot find module '…'require loads only the built-in modules (crypto-js, lodash, moment, uuid, chai, tv4, ajv).
Script stops after a few secondsTime limit of 5 seconds per phase, waits with setTimeout or rt.sleep included; memory limit 64 MiB.
No scripts run in rt runIs --no-scripts set? Assertions still run then.

More in Trust and Postman, Bruno and Insomnia scripts.

A secret is missing or not read

  • Unresolved variable: the report lists placeholders without a value under unresolved. After an import, secrets are created as variables without a value – enter the value once in the environment.
  • External vault (1Password, Vault, AWS, Azure, Google): if the provider’s command line or its login is missing, or the time (60 seconds) runs out, the send stops with exit code 3 and a message saying what to install or which login command to run.
  • In the web app, only the companion reads external secrets, and only with rt agent --allow-secrets.
  • In the pipeline, secrets come as --var NAME=VALUE from the CI job’s variables; a variable given with --var is not read from the vault.

Commit refused

Before every commit, the secret scanner checks the files. If it finds plain-text credentials, the app refuses the commit and shows file, line and kind – never the value. Move the value into a secret variable and write {{name}} in the request. If the line is not a credential, rt-scan:allow (for example as a YAML comment) marks exactly that line, rt-scan:allow-next-line the next one.

Pull, checkout and resolving conflicts refuse while there are unsaved changes, so nothing gets lost: save first, then try again.

OAuth 2.0 in the pipeline

A flow that needs a person (authorization code, device code) would otherwise wait for a browser. With --no-prompt it fails right away instead (exit code 3). In CI, use client credentials or pass a token with --var.

AI agent does not send

SituationCause and fix
Writing request is refusedThe environment allows reading only – that is the default. Set it to Read and write in the Agent access dialog and restart rt mcp (loosening applies only after a restart).
Request hangs, then failsIt is waiting for approval because the environment is marked as production. Click Approve in the app’s banner or use rt approvals and rt approve <id>. After 300 seconds (--approval-timeout) it fails and nothing is sent.
An environment is missing from the agent’s listIt is set to none and hidden from agents.
OAuth sign-in does not startrt mcp starts no sign-in with a browser or a code. Sign in once in the app; the token in the keychain is then used.

Exit codes of rt send and rt run

Codert sendrt run
0A response arrived, whatever its HTTP statusEvery request got a response, every test and assertion passed
1No response: connection, DNS, TLS, timeout, too many redirectsNo network stack could be set up
2Usage error, no collection, invalid files, request not in the collectionUsage error, unknown environment, unreadable data file, report not writable
3Request could not be prepared: unknown environment, invalid URL, auth failed, a plugin or pre-request script stopped itExternal secrets or plugins could not be set up
4A response arrived but a test or assertion failedA request, test or assertion failed

An HTTP 404 or 500 is exit code 0 for rt send – check the status with an assertion or with jq.

Getting help

The core repository takes bugs and wishes as issues once it is published; until then through the contact form. Please never send tokens, passwords or reports with real secret values – RequestTailor’s reports are masked, but a look beforehand does no harm.

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Runner, rt run, JUnit and JSON, exit code 4 ↑Product · RequestTailor core repository, crates/rt-core (runner, assert), crates/rt-cli/README.md (Exit codes) · checked on 2026-11-22

  2. 2

    Secret scanner before every commit ↑Product · RequestTailor core repository, crates/rt-app (secret_scan), crates/rt-cli/README.md (rt scan) · checked on 2026-11-22

Frequently asked

Short answers.

Why is an HTTP 500 not an error for rt send?
Because rt send reports whether a response arrived, not whether its content is right. You check the status with an assertion (then exit code 4) or with jq on the JSON report.
Why does a request fail in the web app that works in the Mac app?
Usually the browser blocks it, for example because of missing CORS headers, or it needs a client certificate. The rt agent companion sends such requests for the web app; client certificates work only natively.
Where do I report a bug?
As an issue in the core repository once it is published, until then through CloudDNA’s contact form. Please do not send tokens or passwords.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.