Skip to main content
First decide whether the message concerns the device, the Agent, the model, or an App, then fix it in the matching place. If a task already has results, check its files and the previous turn before retrying. If you are unsure where each is set up, see the connection checklist.
Open the existing file first and see how far the work got. The model may fail after writing the file but before reporting the result. Do not assume the file is missing just because of the failure label.Retry later, or choose a model that is currently available. When continuing, say clearly: “Check the existing files first and finish only the remaining steps.” Retrieving an instruction only puts it back in the input box. It is not resent automatically.
The current Beta may treat a subfolder inside a Git repository as the repository root. Before sending, check the actual path on the card and in the input box. For practice, unzip materials into a separate folder outside any repository.
Archiving hides the task from the list and stops it. Its record stays in task History. To continue, restore the original task. To pause just one turn, use Stop.
In general tasks that support message editing, editing rolls the conversation context back to before that message. File changes, sent messages, and other external actions remain. Handle them separately through the files or the relevant service.
A regular topic inherits the visibility of its source group, but later only notifies participants. Post in the topic, or join the discussion after someone mentions you.
Check the group or topic for a system message that switched all Agents to Passive. This happens when the number of Agents exceeds the set threshold. You can undo it at that message, or change an Agent’s Listen mode individually. Mentions still work.
Closing the tab only hides the page. To stop its background work, use Quit. To pause the capabilities it gives Agents, switch it off on the App page.
First check whether the device is online and whether the task has work running. Then look for sign-in, network, or quota messages.A Passive Agent in a group needs to be mentioned or replied to. A Proactive Agent may also decide a message needs no answer. To make it act, @ it explicitly and state the task clearly.
Check the install status in the Library and install as prompted. If a provider sign-in is required, sign in on the Subscriptions page, or choose a gugu model that is currently available.For a task on another machine, that machine needs the Agent. Having it installed locally does not mean it is installed remotely.
Check whether you chose your own model or a model provided by gugu. For your own model, check the provider account. For a gugu model, check your gugu membership entitlements and credits.Quotas from different sources are counted separately. If usage fails to load, refresh or repair the connection first. Do not treat an unknown reading as zero.
On the App page, check that it is enabled, that this Agent is allowed to use it, and that the app’s configuration is complete.Controlling the computer also needs Computer Use enabled and system permissions. Accessing external services needs valid account authorization. If a connection just changed, reopen the task and try again.
Check which machine the file is actually on and whether that device is online. gugu shares projects and conversations. Folder contents do not sync automatically.To deliver to other people or another device, use an attachment, a group folder, or an accessible repository. Do not give only a local path.
Retry according to the connection or read error on the page, and check the device the assistant runs on. Failing to read does not mean the data was deleted.Restore the connection first, then look at the original tasks. Do not turn off and set up the assistant again to fix a read problem. Turning it off clears what the page’s confirmation dialog lists.
Check the spelling of your email and your spam folder. Resend when the page allows it. If you already have an account, keep signing in with the original email.
Check the version on the About page in Settings. These docs follow the current Beta. The stable release may not include some new features yet.If differences remain after updating, send feedback from the About page in Settings. Include the version, device, short reproduction steps, and screenshots. Do not include verification codes or keys.

​
When retrying, say where to continue from

Last time the results table was already generated, but the charts weren’t made. Check the existing files first, continue only with the charts, and keep the original data.
If a turn already performed an external action, confirm its result before retrying. A successful tool call completes one step. Check the final deliverable before considering the task finished.