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.
Pausing tracing is narrower than turning tracing off.
saveTrace discards the trace for a whole Run, which also removes the trace you need to debug the other 99% of the automation. Pause when you only need a gap.Available helpers
withTracingPaused— Run a block of code with tracing pausedpauseTracing— Pause tracing until it is resumedresumeTracing— Resume tracing
Function reference
withTracingPaused
callback with tracing paused and resumes tracing when it finishes. Tracing resumes even if the callback throws, so a failure in the middle of a sensitive step can’t leave the rest of the attempt unrecorded.
Prefer this form. Reach for pauseTracing only when the sensitive work spans function boundaries—for example, pausing in a hook and resuming in your automation.
Parameters
() => Promise<T>
required
The code to run with tracing paused.
callback returns.
Example
pauseTracing
resumeTracing is called. Calling it while tracing is already paused does nothing.
Returns
Returns void.
Example
resumeTracing
void.
What pausing covers
While tracing is paused:- Browser trace — No actions, DOM snapshots, or network requests are recorded. The trace viewer shows a gap.
- Screenshots — No screenshots are captured, including the ones taken automatically around actions.
- Automation logs — Anything your code writes to stdout or stderr is dropped rather than stored on the attempt.
- The Run and Attempt records themselves—status, timing, and retry history.
- Your automation’s return value, and the Run’s
parameters. Tracing has no effect on either. To keep a value out of the Run record entirely, use ephemeral parameters. - Errors. A thrown error’s message and stack trace are still stored on the attempt, even if it was thrown while tracing was paused.
Behavior notes
- Nesting works. Nested
withTracingPausedblocks are safe; tracing resumes when the outermost block exits. - Scope is the attempt. Tracing state resets at the start of every attempt, so a retry always begins with tracing active.
- Local development included. The helpers behave the same under
intuned dev, so a locally captured trace has the same gaps a deployed one would. - Ephemeral parameters pause automatically.
getEphemeralParameterpauses tracing on your behalf before it returns a value.
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.