Action Panel

The Action Panel is where you review items that need your attention — blocked Flows, Journeys, and data refreshes that halt downstream syncing until you act, and datastore fields with known data-quality issues.

Flows in Review

Common Flow Errors

Error	Consideration
Flow attempting to add X contacts exceeding maximum allowance Y	Simon uses thresholds (default 30,000) to protect accounts from unexpected contact spikes caused by data integrity issues. You can approve or reject and investigate.
Flow attempting to remove X contacts exceeding maximum allowance Y	Similar protection against unexpected drops in contact volume.
Flow has never been empty before but would be after removing X contacts	Appears when a segment has no contacts to message. Verify your segment parameters before approving. Approval allows the flow to continue without alerts on future empty occurrences.

Thresholds

Flow thresholds protect accounts from unexpected contact volume changes caused by upstream data integrity problems. If you are an account admin, you can manage this threshold via:

Navigate to Settings → Admin Center
Under Campaigns, click on Safety Settings
Modify the threshold and reject timeline.

Upstream Data Issues

To investigate unusual segment size changes:

Review each filter within the segment to assess whether the change makes logical sense
Check the flow's performance tab for historical metrics indicating normal variance
Examine underlying datasets and fields for schema changes

Approve or Reject Flows & Journeys

Navigate to Alerts & Status → Action Panel
Click the Flows tab
Review the flow details, segment information, and error messages
Click Approve to continue or Reject to halt

Approve overrides the threshold violation and allows the flow to proceed as planned. This does not change the threshold itself.

Reject prevents the flow from continuing without deleting the flow or its segments. Flows may return to the panel with new issues.

Automatic Resolution

Flows awaiting manual review automatically reject after 16 hours without user action. The flow becomes ready for its next scheduled run. If thresholds remain exceeded, alerts reappear; otherwise, the flow proceeds as scheduled.

Journeys in Review

Common Journey Errors

Error	Consideration
Segment membership dropped to zero	Review recent segment logic changes. Approving prevents future errors if the segment stays at zero; additional errors occur if the segment rises above zero then drops again.
X new contacts added to segment exceeding maximum allowance X	High contact volume is possible, but exceeding configured thresholds suggests reviewing segment logic to avoid over-messaging.

Approve or Reject Journeys

Open the Action Panel and click the Journeys tab
Review journey details, segment information, and error messages
Click Approve to continue or Reject to halt

Approve proceeds with the journey despite the abnormality. This does not change the threshold.

Reject pauses the journey. You can modify thresholds or segment definitions before the next run to potentially avoid future errors.

Data Quality

The Action Panel surfaces datastore fields with known data-quality problems so you can investigate and resolve them before they affect segments, flows, or syncs. Issues are grouped by error type, with the platform impact and recommended next step shown for each group.

Only fields that currently have a problem appear in the panel — once a field returns to a clean state it drops off the list automatically.

To review issues, navigate to Alerts & Status → Action Panel and open the Data Quality tab.

Error groups

Error group	Platform impact	What to do
Duplicate Join Keys	Queries may return inflated row counts (fan-out), causing incorrect segment sizes and aggregations. For identity datastores, syncs may stall waiting for a contact count that is never reached and require manual intervention to complete.	Fix the upstream data so join keys are unique. If survivorship rules are available for your account, configure them in Datastore settings to deduplicate at query time. While the issue persists, Simon Data selects the first occurrence of each duplicate — note that row ordering in Snowflake is not guaranteed, so results may vary across runs. For identity datastores, contact your Simon Data representative.
Broken View Dependencies	The datastore will fail any query that uses it.	The view references objects that no longer exist. Recreate or update the view definition in your warehouse.
View Column Mismatch	The datastore will fail any query that uses it.	The view's columns no longer match its underlying query. Recreate the view.
Permission Denied	The datastore cannot be read.	Grant the Simon Data service role access to the underlying object in your warehouse.
No Join Key Configured	The datastore cannot be used in any query.	Define a join key in Datastore settings.
Multiple Join Keys	Ambiguous join key configuration; queries may behave unexpectedly.	Remove extra join keys in Datastore settings.
Analysis Timed Out	Data quality is unknown. If duplicates are present, queries may be slow or return incorrect results.	The datastore may be too large for the analysis timeout. Investigate query performance with your data team or optimize the underlying table.
Analysis Failed (Unexpected)	Data quality is unknown.	Contact Simon Data support.

Each row in a group shows the affected datastore and field, and the timestamp of the most recent check. Duplicate Join Key entries also show the number of duplicate keys and rows, and the percentage of duplicate rows.

Notifications

Data quality issues can also trigger Slack and email alerts. See Notifications and Alert History to subscribe.

Additional Notes

Flows and journeys remain visible in the Action Panel for 24 hours after approval or rejection
A pink indicator dot with a count appears when items require review, combining flows and datasets
Click a flow or journey name to view full details, or click a segment name to inspect the segment criteria

Notifications

Alerts for Action Panel events can be delivered via Slack and email. When an error occurs, Slack messages appear in your configured channels. Alerts also appear in Alert History and the Action Panel itself.

To configure which alerts you receive and via which channels, navigate to Alerts & Status → Alert Preferences.