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. Premium gets your own fixed build in 120 minutes, Business a fix within 24 hours, Standard the fix in the next release.
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.

October 2026

Asked	What	Answered
29 Oct, night	A check of how AI assistants cite our pages found 18 pages whose canonical address pointed to a URL that only redirected.	29 Oct, before dawn — canonical links, the sitemap and internal links now point to addresses that answer directly.
25 Oct, afternoon	On a phone, editing a guest document on app.layers.md never reached the file: the browser SumDoc stayed in view mode.	26 Oct, morning — live on app.layers.md: the phone opens the document for editing and the change lands in the file.
25 Oct	Clicking the top edge of a table selected the whole column, and the text typed next silently disappeared.	26 Oct, morning — typing goes into the first cell, as in Word.
24 Oct	“Download” right after an edit in the browser SumDoc gave a .docx without that edit.	26 Oct, morning — the download now waits until the file has been written.
22 Oct	In the integrations stack, hosts that check WOPI proof rejected every SumSheet call; a Frappe site answered 500 when opening a workbook.	22 Oct, same evening — SumSheet and SumDoc sign with one shared proof key; a workbook opens.
20 Oct, night	SumDoc inside Nextcloud showed “read only · list not supported” in the wrong language, and the newest SumDoc image on Docker Hub dated from 1 Oct.	22 Oct, evening — image `sumdoc-webhost:2026.10.22` on Docker Hub.
19 Oct, evening	The app from the Nextcloud App Store would not install on Nextcloud 33–35.	19 Oct, same evening — version 0.1.6 in the store; documents no longer hang on “Loading…” after “Connect”.
19 Oct, evening	In the image built from our Nextcloud recipe, a macro failed with “invalid active cell”.	19 Oct, night — the recipe and kits moved to SumSheet 2026.10.19; the macro runs.
19 Oct, evening	SumSheet inside Nextcloud showed a “Get the app” banner after saving, lost quick typing, and a shape with a macro was only selected instead of running it.	20 Oct, morning — image `2026.10.20b` on Docker Hub: no banner, typing kept, the shape runs its macro.
17 Oct, afternoon	A guest on app.layers.md got the editor in Russian whatever the browser language was.	17 Oct, same evening — the editor takes the guest’s browser language, otherwise English.
15 Oct	A catalogue reviewer took the Thunderbird add-on for “macOS only”: our pages still said “Windows in progress”.	20 Oct — /download and /thunderbird list Windows x64 and ARM64 and Linux .deb and .rpm builds, each with its SHA-256.
15 Oct	In a 14-page contract with track changes on, typing in the browser SumDoc took one letter about every four seconds.	16 Oct — fixed in the engine: the next letter no longer waits for the whole document to be re-read, and a typed letter lands in under a second. 17 Oct — live in the browser SumDoc on app.layers.md.
13 Oct, night	On the SumSheet showcase in the browser, a macro refused to run, the dark theme left some row headers blank, and column widths fell back to defaults because the sheet fonts did not load.	14 Oct, morning — the browser cabins on view.sumoffice.com moved to the current engine: the macro runs, headers are readable in the dark theme, fonts load and widths hold.
10 Oct	After a macro, Ctrl+S on an .xlsm said “Another program changed this file”, and further edits were blocked until the false conflict was dismissed.	11 Oct — SumSheet 2026.4.26.274: the app’s own save of .xlsm and .xlsb is recognised as its own; a real change by another program is still caught.
9 Oct	Macros would not run in desktop SumSheet at all: every Run answered “invalid active cell”. Broken since 24 Sep, while every test stayed green.	10 Oct — SumSheet 2026.4.20.260: the macro starts from the cell you clicked; a new end-to-end test goes through exactly the requests the app sends.
6 Oct	SumSheet did not open a workbook double-clicked in Finder and was missing from “Open With”; on Windows a second double-click started a second copy.	8 Oct — SumSheet 2026.4.13.236: the file opens from Finder and “Open With”, and on Windows and Linux it goes to the window that is already running.
5 Oct	A screen recording from a Mac: after deleting a row, ⌘Z never brought it back, and the header of a second table sometimes vanished by itself.	8 Oct — SumSheet 2026.4.13.236: deleting a row is a step that undo returns, the header stays, and a row border is as easy to grab as a column border.
5 Oct, afternoon	“Check my Excel file” answered “Unreadable” for every workbook.	5 Oct, same evening — a server update had left the package scanner behind; it is back, and the form gives its verdict and the “Open it” button again.
3 Oct, morning	A demo cabin on the showcase stopped opening after it had been idle: everyone who came back to the same link got “the editor did not start”, and only a restart of the service helped.	3 Oct, same day — a cabin that has been put out is no longer handed to the next visitor, and the pool of warm cabins stops holding dead ones. New cabins are live on view.sumoffice.com.
3 Oct	In Thunderbird the second attachment opened in the same session was refused — the first one worked, the next one did not.	3 Oct, same day — SumOffice Local 2026.4.2, signed and notarized, together with the add-on, at sumoffice.com/dl.
3 Oct	The first example on the library pages could not be run: it opened files that only we had.	3 Oct, same day — the sample workbooks and documents are published at sumoffice.com/samples and linked from every library page, with one command that downloads them all.
2 Oct	The library existed for Python only; teams on other stacks had nothing to install.	3 Oct — the same three cores for Node.js, .NET and Java, version 2026.4.3, published in npm, NuGet and Maven Central.
2 Oct	The Thunderbird add-on could not be submitted to the catalogue: it needs a home page and a privacy policy that names the add-on.	3 Oct — the page and a section of the privacy policy are live: what the add-on does, what it sends (nothing to the internet) and why each permission is asked for.
2 Oct	The Python page still said that spreadsheets and presentations were not counted against the free daily quota — that had not been true for a while.	3 Oct — all four library pages say the same thing: opening or saving a file in any of the three cores shares one daily count, and edits inside an open file are free.

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