This feature is in preview. The API may change before general availability. To try it out, contact support@intunedhq.com and we’ll enable it for your workspace.
without_tracing block runs, the browser trace and the automation logs aren’t recorded, so values your automation types or reads there never reach a stored trace or log.
Use it around the few lines that touch secrets: filling a password, entering a one-time code, or reading a record you aren’t allowed to retain.
Pausing tracing is narrower than turning tracing off. Setting
saveTrace to false on the Run request, or defaults.saveTrace in Intuned.json, discards the trace for a whole Run, which also removes the trace you need to debug the rest of the automation. Use without_tracing when you only need a gap.Function reference
without_tracing
async with block, and resumes it when the block exits. Tracing resumes even if the block raises, so a failure in the middle of a sensitive step doesn’t leave the rest of the attempt unrecorded. The exception propagates.
It only has an effect when the attempt is traced. When tracing is off, the block runs normally and its logs are kept.
The TypeScript SDK takes a callback instead:
withoutTracing(fn).What pausing covers
While awithout_tracing block is running:
- Browser trace: no actions, DOM snapshots, screenshots, or network requests are recorded. The trace viewer shows a gap.
- Automation logs: anything written to stdout or stderr, including
printandloggingoutput, is left out of the attempt’s logs. This applies to deployed runs. Underintuned dev, output still prints in your terminal.
asyncio task, is also left out.
What is still recorded:
- What the block leaves behind. A field it filled, or a token still on screen, appears in the first snapshot after the block. Navigate away or clear the field before the block ends.
- The session it creates. Cookies and auth headers on later requests are recorded as usual.
- Your automation’s source code. Traces include the API’s source files, so a secret written directly in your code appears in the trace. Pass secrets in through parameters, an auth session, or environment variables.
- The Run and Attempt records: status, timing, and retry history.
- Your automation’s return value, and the Run’s
parameters. To keep a value out of the Run record entirely, use ephemeral parameters. - Errors. A raised exception’s message and traceback are stored on the attempt, even if it was raised inside the block.
Behavior notes
- Nesting works. Nested and concurrent blocks are safe: tracing pauses when the first one starts and resumes when the last one ends.
- Keep the work inside the block. If the attempt ends while a block is still open, for example in a task that was never awaited, nothing recorded after the block started is kept.
- Each attempt is separate. Every attempt has its own trace, so a retry starts traced.
- Local development included. Under
intuned dev, a locally captured trace has the same gaps a deployed one would.
Related
- Ephemeral parameters: pass secrets to a Run without storing them.
- Monitoring and traces: how traces and attempt logs are captured and viewed.
- Intuned.json reference:
saveTracedefaults for dev and deployed runs.