An AI task stops halfway through a form or document. Starting the same request again can repeat work that already succeeded. OGAD (Off Grid AI Desktop) Pro provides Retry for failed tasks, using the saved progress to help the assistant continue. It still needs to check the current app state; saved progress does not guarantee that every step will be skipped.
| Get OGAD | Desktop releases |
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
What does Retry keep?
The retry carries the task’s saved steps, available step details, summary, and current action back into the runner. It takes a fresh look at the screen or page instead of assuming the old view is still correct. Retry runs on the original execution device.
The first procedure below covers failed-task retry in the stable desktop release. The beta section then shows how to continue a stopped task or choose an earlier saved plan stage.
Recover a small failed task
- Open Tasks and select the failed run in task history.
- Read its last steps and error. Check the target app itself to see what already changed.
- Fix the cause: restore the missing window, finish a required sign-in, select a ready local model, or reconnect a required website.
- Select Retry in the task details on the computer that ran the task.
- Watch the new actions. Use Stop if it starts to duplicate completed work.
- Check the final result in the target app before accepting the task as complete.
For example, if a browser task read two pages and failed to load a third, restore access to that page before retrying. The earlier evidence gives the model useful context. You still need to check that its final table covers all three pages.
Why is Retry unavailable?
A task must be failed in the stable version. An attempt that is still stopping cannot start a second run yet. A task from another device needs that execution device. A missing history record cannot be recovered through this control.
Retry cannot undo an email already sent or a record already created. Check those results before you repeat an action that changes an external service. Describe uncertain outcomes in the chat rather than treating a failure message as proof that nothing happened.
Continue from an earlier stage in the beta
OGAD 0.0.52-beta.102 adds Continue for stopped tasks and a saved-plan-stage menu. Task tools in that beta are available without Pro; the stable Retry procedure above uses the stable Pro task workflow.
Open the task details on its original execution computer. If the run has a saved plan, use the arrow beside Retry or Continue to open Continue from plan step. Select the earlier stage you want to revisit. Only available stages at or before the current plan stage are listed.
For example, after reviewing a comparison table, you may want to return to its checking stage. First inspect what already exists, then select the relevant saved stage. If there is no saved plan or the earlier attempt is still stopping, the menu may not be available. This control does not restore deleted files or roll a website back to an old state.
Reduce repeated actions when resuming
Read the last saved steps and compare them with the current app before continuing. A checkpoint gives the model context; it does not make repeated clicks impossible. The beta also carries verified progress through recovery, but the result still needs a check.
If a task may already have sent a message, submitted a form, or created an item, verify that outcome first. Do not select an earlier stage merely to see whether it repeats successfully. For reversible drafting work, pause if the resumed run begins to overwrite correct content, then give a precise correction before proceeding.
Does retry need the internet?
Local models and local app work can run without a cloud model. A website, remote model, or connected service still needs its connection. The original computer must have the required models, files, permissions, and app state.
Put a limit on repeated chat tool calls
For a chat response that keeps calling tools, open chat settings → Text and review Maximum tool calls. This is an emergency limit on the number of tool calls in one response. Choose a limit that gives the request room to finish, then retry a smaller, clearer task.
The control does not count every mouse or keyboard action inside a Computer Use run. It also is not a time limit, a spending limit, or a way to undo completed actions. Use the task’s Stop control when you need the current run to stop.
If the limit is reached, review what the tools already did before you send the request again. Repeating a task without checking its result can repeat work you did not intend to repeat.
Try OGAD with a small task. If a run fails, inspect its history and correct the cause before using Retry. You get a way to continue with context instead of rebuilding the brief from memory.