Route Editor¶
The route editor lets you review actions captured during a task run and decide which actions should become the saved route for that exact task.
When to open the route editor¶
Open it after the task has run at least once. Even if the task failed at the end, useful captured actions may still be available.
Frontend entries:
- Open task route editor in a scheduled task configuration page.
- Open task route editor in a notification-triggered task configuration page.
Save the task config first
The route editor entry is not shown while creating a new task. The frontend says route editing is available after the task config has been saved once.
Page areas¶
| Frontend area / button | Meaning |
|---|---|
| Task route target | Shows which exact task route is being edited. |
| Saved Route | Shows the route currently saved for this task. If none exists, it says no saved route yet. |
| Current Route | Shows the latest captured actions that are currently kept for saving. |
| Move out of route | Removes an action from the current route. Removed actions will not be saved. |
| Removed from Route | Shows actions removed from the current route. They can be restored before saving. |
| Restore to route | Restores a removed action back into the current route. |
| Save manual route | Saves the kept actions as the task's official route. |
| Finish after replay | If enabled, successful route replay ends the task directly. This option is saved only when you tap Save manual route. |
Basic workflow¶
- Run the task once.
- Open that task's route editor.
- Review actions in Current Route.
- Use Move out of route to remove startup waits, accidental taps, or irrelevant popup handling.
- If you removed the wrong action, use Restore to route.
- Tap Save manual route.
- Run the task again and confirm that route replay works.
Removing noisy actions¶
Remove actions such as:
- Accidental taps.
- Temporary popup dismissals that do not always appear.
- Extra waiting or navigation that is not required.
- Actions performed after the route already reached the desired page.
Keep actions such as:
- Stable entries after the target app opens.
- Taps that enter a fixed tab or fixed page.
- Stable steps needed before the dynamic part of the task begins.
Finish after replay¶
Finish after replay controls what happens after route replay succeeds:
- On: the task ends directly after route replay.
- Off: the task continues into visual execution.
This option is saved together with the route. After changing it, tap Save manual route for it to take effect.
Do not enable it by mistake
If the route only navigates to a target page and the model still needs to fill, judge, or submit something, leave it off. Enable it only when the route itself completes the whole task.
Verify after saving¶
After saving a route, run the task again and check:
- Whether it reaches the target page faster.
- Whether unnecessary model decisions are skipped.
- Whether route replay fails.
- Whether fallback to visual execution works if route replay fails.