Troubleshooting & FAQ — CAPost Documentation

Frequently Asked Questions & Diagnostics

1. Syntax Errors Inside QuickJS Scripts

QuickJS enforces strict ES6+ semantics. To debug errors:

Open the Execution Runner's Console Logs panel to locate the failing stack trace.

Wrap your logic in a try-catch block and output to the console:

try {
    let val = JSON.parse(responseBody);
} catch (e) {
    console.log("Parse failure: " + e.message);
}

2. Request Timeouts on Long Operations

If large file upload API calls or streaming endpoints are timing out too fast, increase the global timeout limit in your environment preset:

environment: Development
variables:
  - key: REQUEST_TIMEOUT_MS
    value: "120000"  # Set to 2 minutes

3. Missing TLS Certificates (Self-Signed Corporate CAs)

If your internal testing environments use in-house self-signed corporate TLS certificates, configure custom CA trust in environment variables or connection settings to prevent TLS rejection failures.

4. Sensitive Secret Injection Failures

If postman.getVaultSecret() fails, verify that you have unlocked your root vault, and double-check that your YAML file references match your exact vault key names.