Back to Field Notes
Log

October 23: an answer that never came, and a forget that needed your exact words

Aria ran out of steps without answering, then sat on a spinner for 3 minutes 42 seconds while one model call ran. And the first real request to forget a note was refused, because the person didn't use the note's exact title.

Covers
Written
Repositories
infinary.io, infinary_controls, kremio, kremio-connect, Orca-strator
Pull requests
29
Reading time
7 min
#aria#reliability#agent-memory#kremio#desk-theme#releases
Contents

29 pull requests merged across five repositories. Most of the day was the 0.22 release train meeting real use on our own ERP site, erp.infinary.io, and two of the things it found are worth telling: an assistant turn that could end without an answer, and a safety rule for forgetting notes that stopped the person it was meant to protect.

PRs merged
29
one model call, behind a spinner
3 min 42 s
model calls per Aria turn
5 → 10
Infinary Controls releases in a day
3

An answer that never came

Two Aria turns on our own site went wrong in two different ways on the same day.

The first was asked how many open Tasks one of our projects has. Aria’s model made five ERP calls through (The Model Context Protocol, an open standard that lets AI apps such as Claude call tools on a server. On our sites, the MCP server is how Aria, our agents and connected AI apps read ERPNext and draft in it.), every one of them successful, and the turn ended with “Aria reached the maximum number of tool steps for this turn.” No answer.

The fix (Orca-strator PR #86) makes the last allowed call the answer. That call still lists the tools, because a Claude model rejects a conversation full of tool calls when no tools are defined, but it sends tool_choice: "none" and a closing note that the budget is used. A tool call on that last call is dropped, not run. Along the way we found that tool_choice was being dropped for the newest Claude models: our code only passed it to models that support forcing a tool, and those models don’t. “None” isn’t forcing anything, so it now goes through for Claude and Gemini alike.

We also raised the budget from 5 model calls to 10. Five meant four rounds of tools before the answer, and a normal ERP question already uses about four. Raising a limit alone doesn’t make an agent use it well, so the model is now told its budget in the system prompt, and each round’s last tool result says how many calls are left. That count goes only into what the model sees. It’s never stored, so the thread keeps the tools’ own output, and it sits inside the history so the cached prompt prefix doesn’t change between calls.

The second turn hung. After five quick model calls, the sixth, to Gemini 3.8 Flash, took 3 minutes 42 seconds to come back with 340 tokens, and all that time the Desk showed a spinner. Our stream loop read the provider’s stream with no time limit at all: the client library’s timeout only bounds the connection setup.

Orca-strator PR #91 gives each model call three limits, all set from the environment:

  • 45 seconds to the first event, whether text, thinking or a tool call. Thinking models can think silently for a while first; 45 seconds covers that and still gives up on a stuck call early. A call that stalls here falls back to the next model, and isn’t retried on the one that just said nothing.
  • 45 seconds between events once streaming has started. Real gaps are seconds long.
  • 180 seconds for the whole turn, model calls and tools together. The ceiling is on the ERP side, where the job relaying the stream is killed at 330 seconds. The worst case, 180 seconds plus a final call’s 45 and 45, stays under it.

When a model stalls mid-answer or the turn runs out of time, Aria keeps what streamed, says the model stopped responding, and makes one last no-tools call to answer from what it found. Every path now ends with a final frame. While a call is slow, Aria sends a “still working” status every 15 seconds, which the Desk now shows under the pending answer, with the seconds waited (Infinary Controls PR #69).

Both fixes are live on erp.infinary.io: the Aria build with them was on our site by the end of the day, with Infinary Controls 0.22.3.

A forget that needed your exact words

Yesterday’s log described the rule for when Aria may forget a note: only when the person’s own words hold a forget verb and the note’s id or full title. It was written to stop text planted in a document or a tool result from deleting someone’s memory.

Its first real use failed. Asked to forget the note “release notes as short bullets”, Aria was refused twice, because the saved note’s title used other words. Nobody remembers a note’s exact title, and nobody should need its number.

So we moved the human check from the words to a click (Infinary Controls PR #68, Orca-strator PR #88, Kremio PR #24). Aria now finds the notes from a plain description and proposes a forget card listing them by id. The site, not Aria, fills the card: it reads each note and keeps it only if it’s the asker’s own personal note, with its real title and an excerpt. Someone else’s note, an organization note, a made-up id or a title Aria invented never reaches the card. Nothing is forgotten until the person clicks Forget on one note.

Remembering had the same problem, more quietly. When a note said more than the person had, it was saved as a Draft “to confirm in My Memory”. We wrote yesterday that this keeps the note from being thrown away. In practice nobody goes and confirms drafts. Now nothing is saved: Aria shows the note on a “Remember for you” card, and one click saves it as the person’s own.

Cards needed one more thing: knowing what the other side can draw. The current Kremio app release, 0.4.0, draws every Aria card as a document to submit. A remember card would have shown up as undefined · undefined, with an Approve button that asks “Submit undefined?”. Nothing would crash, but the person could never confirm the note. Now the app lists the card kinds it can draw in a request header, and the site sends a card only to an app that lists it; older builds get the note as text, saying it’s not saved yet (Infinary Controls PR #66, Kremio PR #23). Orca and the site do the same handshake for the new cards, because one Orca serves sites on every version.

The site side is in Infinary Controls 0.22.3, on our own site. The app side is Kremio 0.5.0, so far a test build.

Also

  • Every Decision and Preference note went Stale overnight. Agent Memory’s daily job marks notes past their review date as Stale. Those notes have no review date, and Frappe, on 15 and on 16 alike, compiles the date filter so that a missing date counts as the year 1. It hit our own site too, on Frappe 16. The filter now requires a date (Infinary Controls 0.22.2). The same release makes the fallback search match word by word, so “quotes eur” finds “Quotes in EUR”, and fixes a fresh install on Frappe 15.
  • A date mask that skipped the dates. The Desk theme bench reported a changed screenshot for the invoice report every day. Its date mask skips any element whose text is over 80 characters, and the report’s date cells are padded past that, so real dates stayed in the shot. Cells are now masked one by one, and the capture fails if any date is left (PR #310).
  • Containers racing to fill a volume. Our upgrade rehearsal couldn’t start from a client image, with “file exists” errors. A client image bakes its assets into the sites directory, and docker compose up starts several containers on the new empty volume at once, each copying into it. Limiting Compose’s parallelism didn’t serialize them. The script now creates and fills the volume once, before up (PR #312).
  • Staff can remove staff-only apps. Until now staff could install an app we don’t offer to customers, but nobody could remove it. The new removal goes through the same request as a customer’s: a count of what would be deleted, the app’s name typed, a snapshot first and a restore if it fails (PR #308).
  • An audit of our own. We ran a features, security and user-flows review of the platform. Fixes for several findings merged the same day in four repositories and are deployed. We’ll write about it once every finding is closed.
  • Releases: Infinary Controls 0.22.1, 0.22.2 and 0.22.3; Kremio Connect 0.9.1; Kremio 0.5.0 as a test build. The fleet image with Controls 0.22.3 and Kremio Connect 0.9.1 passed the Desk bench, with one German screen moving a pixel or two, approved by hand (PR #319).