Purpose
This article helps troubleshoot scenarios where Prospect output files are not delivered, even though the source file exists or was previously sent.
Scope
This applies to:
Prospect output orchestrations
Automated monthly or quarterly Prospect workflows
Fully automated courier-based ingestion processes
Symptoms
You may observe one or more of the following:
Prospect output files not received by the expected date
Workflow fails due to source file not found
Source file was delivered earlier than expected
No recent Prospect outputs despite prior ingestion
How Prospect Workflows Typically Work
Prospect outputs are generated by an automated workflow
The workflow:
Runs on a defined schedule window
Looks for files delivered within a specific lookback period
Output files are generated only after a successful Full Workflow run
Common Causes
1. Source File Delivered Outside Workflow Window
If a file is delivered earlier than the workflow’s lookback range, it may not be picked up automatically.
Example:
File delivered before the workflow’s scheduled window
Workflow does not detect the file and fails with “file not found”
2. Ingest-Only Runs Do Not Trigger Outputs
If a file is ingested using:
Ingest Only, or
Run directly from a Courier (not Courier Group)
then downstream orchestrations will not run automatically.
3. “Abort When Missing” Configuration
If the workflow is configured to:
Abort when any expected file is missing,
then the entire workflow may fail even if one valid file exists.
4. Cadence Mismatch (Monthly vs Quarterly)
If the source data is delivered on a quarterly cadence, but the workflow is configured to run monthly:
The workflow may run without finding files
This does not cause data loss but may delay outputs
Recommended Self-Checks for Customers
Before contacting Support, verify the following:
- Confirm the actual delivery date of the source file
- Check whether the file falls within the workflow’s lookback window
- Verify whether the ingestion was:
Full Workflow
Courier Group run
Not Ingest Only - Confirm cadence alignment (monthly vs quarterly)
- Check whether orchestrations were triggered after ingestion
How to Recover Outputs
If the source data was successfully ingested earlier:
The Prospect Outputs Orchestration Group can be manually triggered
Outputs will reflect the current state of downstream datasets
This may differ slightly from the original ingestion-date snapshot
When to Contact Support
Contact Amperity Support if:
You are unsure whether the file was ingested via Full Workflow
Outputs remain missing after confirming ingestion
Workflow configuration needs adjustment
Providing the workflow name and ingestion date will help expedite resolution.
Summary - Missing Prospect outputs are often caused by timing or configuration, not system failures
- File delivery outside workflow windows is a common cause
- Ingest-only runs do not trigger orchestrations
- Most issues can be identified and resolved without platform changes