Documentation
Learn how to configure capture schedules, timezones, trigger windows, and cloud storage — from first setup to production workflows.
Browse sections
Need help?
Contact SupportRetry & Stability
Modern websites are dynamic and sometimes unreliable. Retry & Stability controls help ensure captures succeed even when pages are slow, flaky, or temporarily unavailable.
Retry & Stability features focus on consistency. When a capture fails due to temporary issues, the system can retry automatically instead of producing a broken or empty result.
Why retries are needed
Even well-built websites can fail intermittently. Retries help smooth over short-lived issues without manual intervention.
- • Temporary network errors
- • Slow backend responses
- • JavaScript-heavy pages still loading
- • Third-party scripts timing out
Retry behavior
When enabled, retries follow a controlled execution flow.
- 1. Capture attempt starts
- 2. Page load or render fails
- 3. Attempt is marked as failed
- 4. System waits briefly
- 5. Capture is retried automatically
If all retry attempts fail, the capture is marked as failed and logged for review.
What is retried
Retries apply to the entire capture execution, not just the final screenshot step.
- • Browser startup and navigation
- • Page loading and rendering
- • Selectors and interactions
- • Screenshot or video generation
Stability vs retries
Retries fix temporary failures. Stability settings help prevent failures in the first place.
Stability controls
- • Page timeout
- • Scroll delays
- • Selector waits
- • Trigger Windows
Retries
- • Recover from failures
- • Automatic re-execution
- • No manual intervention
- • Logged for visibility
Example scenario
A schedule runs hourly on a dashboard page. Occasionally, the backend API responds slowly and the page fails to load within the first attempt. Retry logic automatically re-runs the capture, producing a valid screenshot without manual action.