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 sendandrt run - Web app
- the
rt agentcompanion 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.
- Start
rt agentin a terminal. - In the web app, choose Send through companion and, the first time, enter the Pairing code from the terminal.
- 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
| Situation | Cause and fix |
|---|---|
| Banner “This collection contains scripts. Run them?”, report with a warning note | You 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 seconds | Time limit of 5 seconds per phase, waits with setTimeout or rt.sleep included; memory limit 64 MiB. |
No scripts run in rt run | Is --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=VALUEfrom the CI job’s variables; a variable given with--varis 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
| Situation | Cause and fix |
|---|---|
| Writing request is refused | The 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 fails | It 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 list | It is set to none and hidden from agents. |
| OAuth sign-in does not start | rt 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
| Code | rt send | rt run |
|---|---|---|
| 0 | A response arrived, whatever its HTTP status | Every request got a response, every test and assertion passed |
| 1 | No response: connection, DNS, TLS, timeout, too many redirects | No network stack could be set up |
| 2 | Usage error, no collection, invalid files, request not in the collection | Usage error, unknown environment, unreadable data file, report not writable |
| 3 | Request could not be prepared: unknown environment, invalid URL, auth failed, a plugin or pre-request script stopped it | External secrets or plugins could not be set up |
| 4 | A response arrived but a test or assertion failed | A 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
- Docs Companion rt agent
- Docs Scripts, tests and runner
- Docs AI agents and MCP server
- Docs rt command line
- Sources rt-cli/README.md1 · rt-cli/README.md2