Pit stop: what was asked, and when the version answered

A tool should change under your work, not the other way round. This board is the proof, kept as it happens: a request from a person — a bug, a file that did not open, a behaviour to change — and the version that answered it, with both times. Our own defects are fixed for free. Changes under your process are ordered by class with a date and a person responsible. Nothing here is edited afterwards.

How it works

Intake — the assistant inside every editor (desktop, mobile, browser, Nextcloud): “Report a problem” or “Request a feature”, with the file if you allow it. Business and Premium plans get a deadline; Free is looked at in turn.
Answer — a version. For server images that is a new tag on Docker Hub the same day; for the apps — the next store build; for the browser editors — the live cabins.
Board — one line per request: what, when asked, when shipped. Names of people and companies are not shown; the file never is.

September 2026

Asked	What	Answered
22 Sep, morning	The MCP connector on a public registry showed “unhealthy” (HTTP 503): crawlers had used up every session slot, so real clients were refused.	22 Sep, within two hours — sessions and editor cabins are now limited separately (40 / 5) and idle sessions expire in 3 minutes; seven connections in a row answer 200.
21 Sep, afternoon	The Agent panel in a browser cabin refused a user’s own uploaded document (“unknown document”).	21 Sep, within the hour — the panel serves any opened file; verified on an uploaded .docx.
21 Sep, afternoon	On a phone, the assistant window called itself by the engine’s internal name and the Agent button covered its “send” arrow.	21 Sep, same evening — both fixed on all SumDoc lines; the fix mirrors the SumSheet one.
21 Sep, morning	A billing export that Excel offered to “repair”: two damaged package parts, a worksheet garbled from row 2865.	21 Sep, same day — Check reports the damage by rows and returns a repaired copy (rows 1–2864 and 4097 onward intact); Excel opens it without a dialog. Became the repair door.
21 Sep, afternoon	The documentation assistant on docs.sumoffice.com answered “unavailable”.	21 Sep, within the hour — it answers with sources again.
20 Sep	An .ods workbook hung the engine on open.	20 Sep, same day — an endless scan of an external `file:///` reference; fixed in the engine, plus an .ods → CSV tool.
20 Sep	An empty .docx (no body) could not be opened.	20 Sep, same day — the package gets a body on entry; opens everywhere.
20 Sep, night	“Open it” on Check answered 502 for everyone at once.	20 Sep, same night — one out-of-memory engine was taking the whole line down; the line now keeps running and the one cabin restarts.

Times are Europe/Madrid. Entries are added when the version ships, never before. Made by SumOffice · SumOffice Embedded · how changes are priced · Contact