Troubleshooting

A run stopped partway

Skipped steps, timeouts, and a task that ends earlier than expected.

“That control wasn’t where the page said it would be — the step was skipped.”

Why: The page changed between the plan being made and the step running: a dialog opened, a section collapsed, a list re-ordered.

Fix: Ask again from where the page is now. A fresh plan is built against the page as it currently stands.

“The page didn’t respond in time — the step was skipped.”

Why: The step ran, but the page was still loading or working when the deadline passed.

Fix: Wait for the page to settle and ask again. On a consistently slow site, Guide mode avoids the deadline entirely.

The run ended and said the task was already done

Why: A continuation round came back containing only steps that had already been carried out. Tabruns refuses to start a round that repeats its own work, and ends the task instead of looping.

Fix: Check the page. Usually the work is genuinely finished. If something is actually missing, ask for that specific thing.

A step says “declined”

Why: You said no to it, or to the confirmation in front of it.

Fix: Nothing to fix — declined steps are recorded as declined, and never counted against the run's success.

A stopped run is not a rolled-back run. What was done stays done; use Undo on the receipt to reverse the fields it filled.