These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Job added to a host
- No central list
- It stops silently
- Someone asks for the report
With SynaptaGrid
- Schedule is a trigger
- Listed with its run history
- Retry and timeout handled
- Failure raises a notification
The situation
They accumulated one at a time, each on whatever host was convenient. There is no single list of what runs where, nothing raises an alarm when one does not run, and the logs are wherever that machine writes them. Some of them have outlived the reason they were written.
How it is approached
A schedule is a trigger on a workflow — a cron expression, a fixed interval, or once at a set time — so scheduled work appears in the same list, with the same run history, as everything else. Each run records its steps, inputs, outputs and errors. Failures retry on a widening backoff, background sweepers time out a run that overran, and notification on failure, timeout or a stalled run is configured rather than written.
What changes
What runs on a schedule becomes a list somebody can read, with its last run against it. A job that stops running raises a notification instead of waiting to be noticed.