Skip to main content
Production browser workflows should retry deliberately. Some failures are transient. Others are policy decisions, user-denied approvals, blocked pages, invalid input, or site behavior that should stop the job.

Retry guide

Redacted logging

Log bounded, redacted fields rather than raw browser errors.
Raw browser errors can include page content, URLs, local paths, request fragments, or signed capabilities. Redact before storing or sharing.

Preserve evidence

When a job fails, keep the evidence that helps someone decide the next step:
  • Browser ID.
  • Final status.
  • Redacted error code and message.
  • Step summaries or observations.
  • Relevant artifact IDs.
  • Recording segment IDs when recording was enabled.
Reference: observability, error codes, status, events, and logs, and blockers and CAPTCHA.