This article covers:
The run failed, with no segment created
The run finished with 0 fans, or a red X on a child segment
The segment built but the push to your destination failed
Which of the four error categories, System, Configuration, Schedule, or Destination, you're looking at
Re-running a failed or skipped run
In short
Every automation failure falls into one of four categories: System, Configuration, Schedule, or Destination. System errors and some Destination errors often clear on their own or with a re-run. Configuration and Schedule errors need something fixed before a re-run will succeed. You can re-run any failed or skipped run from the automation's run history, for both time-based and event-based automations.
What you see
What you see | What it means | What to do |
The run failed | No segment was built. The error names the category. | Find the category below, then read its article. Fix a Configuration or Schedule problem first, then select Re-run. A re-run against the same setup fails the same way. |
The run finished with 0 fans | Not an error. Either nobody matched, or a data source returned nothing. The run is marked as skipped. | Check your data sources. If data arrived late, select Re-run on the skipped run once it has loaded. Otherwise no action is needed. |
A red X on a child segment | Not an error. The automation ran but no fans matched the criteria. | Same as above. Loosen the criteria if you expected fans, or re-run once late data has loaded. |
The segment built but the push failed | A Destination error. Only the handoff failed, so your audience is safe in Segment Analyzer. | Fix the destination problem, then select Re-run to push the same segment again. See that destination's article. |
Will retry on a push | A Destination error StellarAlgo is already retrying by itself. | Wait. No action needed. |
The four categories
System. A short-lived processing problem while the segment was being built, not caused by your setup. See Troubleshooting system errors.
Configuration. Something in the automation's own setup is invalid, incomplete, or points to something that no longer exists. This never clears on its own. See Troubleshooting configuration errors.
Schedule. The event couldn't be matched to your league schedule, or its details haven't arrived yet. See Troubleshooting team / league schedule errors.
Destination. The push failed on authentication, a mapping, a missing list, or the destination being unavailable. Each destination connects and fails differently, so see Push destinations for the specific one.
Re-run a failed or skipped run
You can re-run any failed or skipped run, for both time-based and event-based automations. There is no time limit. What a re-run does depends on why the original run did not complete.
Run status | What a re-run does | Before you re-run |
Failed with a Destination error | The segment was already created, so it is not rebuilt. StellarAlgo pushes the same segment to your destination again. | Fix the destination problem, for example reconnect the destination. |
Failed with a System, Configuration, or Schedule error | No segment was created the first time, so the re-run builds it now, using your criteria and data as they are at the time you re-run. For an event-based automation, it is still tied to the original game. The segment is then pushed to your destination. | Fix a Configuration or Schedule problem first. A System error usually needs no fix. |
Skipped, with 0 fans | The segment is built now, using your criteria and data as they are at the time you re-run, then pushed if fans match. The re-run replaces the skipped run in the run history. If still no fans match, it is marked as skipped again. | Confirm the data you expected has loaded. |
To re-run:
From the Segmentation menu, select Automations, then open the automation.
In the run history, find the failed or skipped run.
Select Re-run.
Note: When a re-run builds a new segment, fans are matched as of the re-run, not the original run time. For criteria tied to recent activity, that can return a different group of fans. See How automations run.
Things that fail silently
These show no error anywhere, so they arrive as a suspicion that the numbers are wrong.
A suppression or exclusion list that matches nobody. The send still runs and nothing is flagged. This is usually an identity matching problem, and you cannot fix it from your side, so contact support.
Late arrivals in a destination list. If a tracking window stays open after the game, fans keep landing in the list after you expected it to close. Tighten the window.
An audience that looks wrong after a re-run. The criteria were re-evaluated at the new time, not the original one. See How automations run for why that happens.
A run that happened before your data arrived. The run succeeds and the audience is simply smaller than it should be. Nothing is flagged, so compare the count against what you expected rather than against an error.
FAQ
How do I know which of the four categories my error is?
The error text names it directly. If you're not sure, check the What you see table above.
Can I re-run a failed automation?
Yes, for both time-based and event-based automations, with no time limit. Select Re-run on the failed run in the run history. A Destination failure pushes the existing segment again. A System, Configuration, or Schedule failure builds the segment at the time you re-run.
Can I re-run a skipped run?
Yes. Select Re-run on the skipped run. The segment is built at the time you re-run, and the new run replaces the skipped one in the run history.
Still need help?
Contact StellarAlgo support and include:
The automation name
The error category, if the error names one
The date and time the error occurred
The destination name, if it's a Destination error
Whether you have already re-run it