Browser Journeys
Scheduling
Configure when and how often your journeys run with intervals and cron schedules.
Scheduling
Configure when your journeys run using simple intervals or flexible cron expressions.
Schedule Types
Interval Scheduling
Run journeys at fixed intervals:
| Interval | Runs per Day | Best For |
|---|---|---|
| 1 minute | 1,440 | Critical paths, real-time monitoring |
| 5 minutes | 288 | Important flows |
| 15 minutes | 96 | Standard monitoring |
| 30 minutes | 48 | Less critical paths |
| 1 hour | 24 | Low-priority checks |
Cron Scheduling
For more control, use cron expressions:
0 9 * * 1-5 # 9 AM, weekdays onlyCron Expression Format
┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-6, Sunday=0)
│ │ │ │ │
* * * * *Common Cron Examples
| Schedule | Cron Expression | Description |
|---|---|---|
| Every hour | 0 * * * * | At minute 0 of every hour |
| Daily at midnight | 0 0 * * * | 12:00 AM every day |
| Daily at 9 AM | 0 9 * * * | 9:00 AM every day |
| Weekdays at 9 AM | 0 9 * * 1-5 | 9:00 AM Monday-Friday |
| Every 6 hours | 0 */6 * * * | At 00:00, 06:00, 12:00, 18:00 |
| First day of month | 0 0 1 * * | Midnight on the 1st |
| Every 15 minutes | */15 * * * * | :00, :15, :30, :45 |
Use crontab.guru to build and validate cron expressions.
All schedules run in UTC.
Run Locations
Choose where to run your journey:
- Global - Automatically selected region
- US East - Virginia
- US West - Oregon
- EU West - Ireland
- EU Central - Frankfurt
- Asia Pacific South - Singapore
- Asia Pacific Northeast - Tokyo
Pause and Resume
Manual Pause
Temporarily stop a journey without deleting it:
- Go to the journey
- Click Pause
- Journey stops running but configuration is preserved
Run Settings
| Setting | Description |
|---|---|
| Timeout | Maximum duration for a single run |
| Max Retries | Number of retry attempts on failure |
Triggering Runs
Manual Trigger
Run a journey immediately:
- Go to the journey
- Click Run Now
Schedule Best Practices
1. Match Interval to Criticality
| Criticality | Recommended Interval |
|---|---|
| Critical (checkout, login) | 1-5 minutes |
| Important (core features) | 5-15 minutes |
| Standard (other features) | 15-30 minutes |
| Low priority | 1 hour |
2. Set Realistic Timeouts
Allow enough time for slow networks, page load times, and third-party service responses.
3. Account for Dependencies
If journey A depends on data created by journey B, schedule them with a time gap:
# Journey B: Create test data (runs first)
0 */4 * * * # Every 4 hours
# Journey A: Uses test data (runs after)
5 */4 * * * # 5 minutes after B