The Auto-Pause Notifications feature provides an additional layer of protection for Journey integrations by automatically disabling integrations that experience a high volume of errors.
This prevents invalid submissions from continuously being processed and immediately alerts administrators when corrective action is required.
Why This Feature Matters
Configuration issues, invalid mappings, or incorrect data can sometimes cause integrations to repeatedly fail.
Without intervention, thousands of failed submissions could continue processing, resulting in:
Lost leads.
Increased troubleshooting time.
Unnecessary API activity.
Difficulty identifying the original issue.
Auto-Pause Notifications help prevent these situations by automatically stopping problematic integrations and notifying the appropriate users.
Accessing Auto-Pause Notifications
To configure notifications:
Navigate to My Journeys.
Open the desired Journey.
Select General Info.
Scroll to the Auto-pause notifications section.
Enter the email addresses that should receive alerts.
Click Add.
Optionally enable: Also notify the location owner.
Click Save.
How Auto-Pause Works
The system continuously monitors Journey activity. If a Journey encounters 5,000 errors within a one-hour period, the system will automatically:
Pause the Journey.
Stop processing new submissions.
Send notification emails.
Prevent additional failed requests.
The Journey remains paused until it is manually reactivated.
Email Notifications
When a Journey is paused, email notifications are sent to:
Configured notification recipients.
The location owner (if enabled).
These notifications allow administrators to quickly investigate and resolve the issue.
Reactivating a Journey
After resolving the issue:
Open the affected Journey.
Review the identified errors.
Update the necessary configuration.
Manually reactivate the Journey.
Once enabled, the Journey will resume processing new submissions.
Note: Auto-paused Journeys do not automatically resume. Manual reactivation is required after the issue has been resolved.
Best Practices
To reduce the likelihood of auto-pauses:
Regularly monitor the Journey Dashboard.
Review Partial and Failed submissions.
Validate field mappings after changes.
Monitor high-volume integrations.
Configure multiple notification recipients for faster response.
Key Benefits
✔ Prevents large volumes of failed submissions
✔ Provides early visibility into integration issues
✔ Reduces troubleshooting time
✔ Protects lead data from repeated failures
✔ Helps administrators respond quickly
✔ Improves overall Journey reliability