Private build · First look
Plan runs.See results.
Choose a record source, the automation to run, and the schedule. tiq handles the batches and gives every record a visible outcome.
A live preview of a tiq scheduled job: it resolves a set of records from a report, runs an action across them in batches, and reports how many records succeeded and how many failed.
The live instrument alternates between a clean run and a partial run so failure stays legible. Reduced motion shows a completed snapshot.
Three inputs.One trace.
A job asks only for what the engine needs, in the order the engine needs it.
- 1
Source
Which records?
Point tiq at a report, list view, or SOQL query. The target count is visible before anything runs.
- 2
Action
What happens?
Run a Flow or invocable Apex against the set. Map source fields or fixed values to the inputs.
- 3
Schedule
When does it run?
Run on demand or set a dependable cadence. Every execution leaves an accountable result.
Keep logic.Drop plumbing.
The trusted model stays. The legacy plumbing does not.
Newton’s release test
Show the count before the run. Account for every record after it.
A scheduled batch that silently half-finishes does not pass inspection.