Otto said he'd "keep this queued" until a connection is back - will he actually pick it up?

Otto stops in the middle of something and tells you a connection is down. The message reads close to this: "That connection's still down - I can't reach the digest tool itself yet, so I can't finish the sender-identity fix or reclassify the last few items. I'll keep this queued and pick it up as soon as it's back; no need for you to do anything in the meantime." So you take him at his word and leave it alone. Days later the work still is not done. If your read on this is that Otto said he would do it later and never did, that is a fair read, and this article is for you. It covers what that sentence does and does not promise, and the two screens where you can check for yourself in about a minute.

What the message is claiming

There are three separate claims packed into one friendly sentence, and they are not equally reliable:

• A tool or connection he needs is not reachable right now. This part is usually true and is worth checking on the Connections tab.
• Two specific pieces of work are therefore unfinished: a sender-identity fix, and a request to reclassify the last few items.
• He has queued that work and you do not need to do anything. This is the claim to check.

The honest answer: is the work actually queued?

A sentence Otto types in chat is Otto reasoning out loud about what he intends to do next. It is not the app scheduling anything. Otto's own operating rules say it plainly for his written notes too: his notes are claims, not proof. The same applies to a promise in a chat bubble.

Work provably exists in one place, and that place is the Tasks tab. Two things put an item into Scheduled next there: a Play you switched on under Settings > General > Plays that may start themselves, once the app notices the real event that Play watches for, and a scheduled task you added under Settings > General > Runs on its own. Otto describing something as queued in a chat message is neither of those. If you cannot see the item on the Tasks tab, treat it as not scheduled.

There is one real thing Otto can do when he has to stop: park the item as a decision for you. When that happens it appears in Needs your decision on the same tab, with a line saying what it needs from you. So both honest outcomes, scheduled or parked, land on one screen. Neither of them is invisible, and neither of them lives only in the chat transcript.

If this pattern is new to you, it is the same habit that applies to any figure or status Otto reports conversationally. See Can I trust Otto's numbers? Where the app is exact, and where Otto can be wrong for the wider version of this.

Step 1: check the Tasks tab

1. In the right pane, click Tasks. You can also land here from the Today tab with See every task.
2. Read Scheduled next. This is queued and recurring work. If the thing Otto promised to resume is genuinely scheduled, it is listed here with its time. If it is here, believe it: this list is fed by the app, not by the conversation.
3. Read Needs your decision. Work that stopped safely and wants a choice from you sits here, including anything Otto parked deliberately rather than retrying on its own.
4. Glance at Otto is handling. If something is genuinely still running, it shows here rather than in either list above.
5. Read Completed. Its subtitle is Recently verified work on purpose: a run lands there when it finished cleanly and the app saw its done signal, and its card then reads Verified complete. Read the line on the card rather than the section name, because the app also files items here that it closed out without running them, with a line like No longer needed; the original trigger has changed.

If the promised work is in none of those four lists, nothing is holding it. That is not a bug you need to report before you can move on: it means the work will need to be asked for again once the connection is back.

Step 2: read the badge on the affected connector

Open the Connections tab and look at the badge on the connector Otto was reaching for. The badge tells you how much the app actually knows:

• Connected (green): the app checked for a live presence on this computer and the check passed. This is the strongest badge.
• Key saved or Login saved (amber): a key or account is stored in the encrypted vault, but it has never been tested against the service. It is proven the first time Otto uses it, so it can still turn out to be expired or wrong.
• Linked (dim): the connection lives at the account level, not on this machine, and has never been checked live. It means "this was linked at some point", nothing more. A Linked service can fail while the badge still looks fine, which is exactly how you end up with a working-looking Connections screen and an Otto who cannot reach anything.
• Not yet: nothing is set up for this connector.

If Gmail or Google Calendar shows Linked

Almost everyone tries to fix this by relinking the account on claude.ai. That is a dead end. The linked-account path is not the supported route for Otto's mail and calendar work, and relinking will not make it reliable. Skip it and connect directly instead:

• Gmail: add the inbox under Connections > Mail & calendars as an Any email (IMAP) account using a Google App Password. Full steps are in Connect your Gmail with an app password (step by step).
• Google Calendar: add the calendar's private ICS link in the same Mail & calendars section. That feeds Otto's agenda and date clash checks directly.

Once those direct connections are in place, the claude.ai connectors can stay disconnected.

What "the digest tool" means, honestly

That phrase is Otto's own wording for something he was reaching for internally. There is no button, tab, or screen in the app called the digest tool, so do not spend an evening hunting for one. From the message alone we cannot tell you with certainty which piece failed.

What we can tell you is where to look. The Inbox tab is your support digest: every conversation the app has taken in, sorted into six groups (Needs you, Reply ready, Waiting on them, Follow ups, Handled, All good). A request to reclassify the last few items is a request to move items between those groups, so the Inbox is the surface where you would see whether it happened. Open it and look at the groups yourself rather than trusting a summary in chat.

What does resume on its own, and what never does

An automatic resume genuinely exists, but only for background jobs the app itself started, and only for one class of them:

• Jobs that cannot send anything (drafting, research, organizing) retry on their own up to 3 times with growing gaps between attempts. After that they stop with Needs a look before it runs again.
• Jobs that may send a message are never replayed automatically. If one is interrupted, it is marked failed and parked in Needs your decision so nobody gets contacted twice. You review, then re-run it by hand.

Neither of those mechanisms is triggered by Otto saying the word queued in chat. They apply to work the app was already tracking as a job.

The other queue, which is real

There is a queue in chat, and it is worth knowing the difference so the words stop being confusing. Messages you type while Otto is mid-task are held and sent the moment he wraps up. Those are visibly marked queued in the conversation, and a note under the message box counts how many are waiting. That queue is a real mechanism with a real indicator on screen. Otto describing his own unfinished work as queued has no such indicator, which is the whole difference. One more thing worth knowing: if you press Start fresh, any messages still waiting are cleared and will not be sent.

When the connection is back

1. Open Connections and confirm the connector now reads Connected rather than Key saved or Linked.
2. Go back to chat and ask for the unfinished work by name, in one specific sentence. For the message above that would be a request to finish the sender-identity fix, and a separate one to reclassify the items in the Inbox. Naming the exact thing beats asking him to "pick up where you left off".
3. Use Watch live work in Activity from the Tasks tab if you want to see it happen step by step instead of reading a summary afterwards.
4. Confirm the result on the screen where it should show up, not in Otto's recap of it. For a reclassification, that is the Inbox groups.

If it still does not work

This exact message has not been fully diagnosed yet, and real examples are what will close it. If it repeats, send us a ticket with three things: the message text exactly as Otto wrote it, the badge state of the connector it named, and a support bundle.

1. Open Settings > General and switch on Support logging in the support section.
2. Reproduce the problem once with logging on.
3. Return to Settings > General and click Generate Support Bundle, then attach the file to your ticket. Your saved API keys are never part of the bundle.

Still stuck? Email bookedsolid@kivimedia.freshdesk.com and a person will help.