Destinations health checks
The destinations health check scans your sandbox for destination activation schedules with an expired end date whose dataflow remains active.
Check
Object type
Destination
Stale destination schedules stale-destination-schedules
Identifies destination activation schedules that are considered stale because their configured end date is in the past while the dataflow remains active.
Detail
Description
Issue
One or more destination activation schedules have a past end date but the dataflow remains active.
Impact
The dataflow stops exporting data, and you might wonder why your campaign stopped receiving data.
Remediation
Extend the expired end date, create a new dataflow, or remove the dataflow.
When you select the Stale Destination Schedules card, a detail panel opens on the right. The panel shows:
- Description: Explains that the configured activation end date is in the past while the dataflow is still active. This check inspects existing destination activation schedules for this condition.
- Impact: The dataflow stops exporting data, and you might wonder why your campaign stopped receiving data.
- General areas of impact: Destination activation schedules.
- Experience League documentation: Links to schedule audience exports for streaming and batch destinations.
- Recommendation: Extend the expired end date, create a new dataflow, or remove the dataflow.
- Affected flows: A list of active dataflows with audiences that have a past activation end date, including the associated audience and expired end date. Use the link icon to open the flow.
For more information, see how to schedule audience exports for streaming and batch destinations.
Next steps next-steps
- Return to the health checks overview to explore other check categories.
- Review the scheduling documentation for streaming and batch destinations to manage your destination dataflow schedules.
recommendation-more-help
experience-platform-help-run-and-operate