Pre-execution
At launch, Telepúrte checks the user, targets, agent status and resolution of each step, preview captures the exact version of the script and node, lasts ten minutes, its confirmation checks the current state. If you change your version, access, agent, or policy, you get a new preview: a new machine that appears in the group after confirmation is not added to the task you’ve already created, and a repeat confirmation of the same preview by the author returns the previous task, rather than creating another one. One run supports up to 100 nodes. For a large group, divide the work into meaningful sets and check the result between launches.What happens after confirmation?
The task gets in line. The agent gets the work for his node, takes the step and reports the result. The next step on this machine opens after the successful previous one. Without an explicitly specified rollout, normal goals are independent, output is limited to sequential mode. A single node error is not a promise of automatic cancellation of all others. A separate rollout rule is needed to stop by canary and error threshold. Before issuing a step, the rights and policy are checked again, revoking access between steps prohibits the next step, but the action already taken by the agent may have time to complete.Task card
Open Playbooks and Schedules → Executing Tasks or Launch History. The list is updated automatically, you can update it manually. In the card, see not only the general status, but also each goal.
A common “completed” does not replace application verification. A service can be active but return an error to users; a script can return a zero without verifying its business result.
Canary and parties via API
The preview API supportsrollout. This is an extended mode; the current conventional run wizard does not offer separate canary and threshold fields.
Stoppage.
In the active task card, request a stop. Telepúrte stops issuing new actions, waiting for the goal to be canceled. The action already transmitted to the agent does not turn into “not completed”: it can be completed after pressing a button. For a job that hasn’t started completely, you can cancel it before you get your first job. For someone who’s already working, use the stop and wait for the results of what you’re doing, and closing the tab doesn’t replace that.Lost result and repetition
For a reading operation, it is permissible to reissue after a loss of response. For a change, Telepúrte does not assume that no response means no effect: the result becomesexecution_uncertain.
With this result:
- Stop spreading the change further if it is still in progress.
- Check a specific node with an independent state reading.
- Determine which steps have actually been completed.
- Fix the link or the policy.
- Create a new launch just for the job you need.
