WeDispatch 1.5.2: the status page now watches text preparation too
The /status page tracks four services instead of three. Text preparation is verified by a real call, not by a box ticked somewhere in the configuration.
A status page is only worth what it watches. Ours showed three lines: the site, the database, speech synthesis. One was missing — the step in between, the one that reads and reshapes your article before any voice pronounces it. It has been there since 1.5.0, it decides where your text is processed, and it appeared nowhere on /status. That is now fixed.
A fourth line, and why it matters
Text preparation is the step that cleans up the article, pulls out the useful content, produces the express summary and describes your images. It now has its own line on the status page, ranked alongside the database and the voice.
This is not cosmetic. The standard and premium tiers allow a fallback: if that step is briefly unavailable, your generation carries on instead of failing, and the audio's provenance record says so in plain words. The mechanism protects your output — but a service that quietly catches itself is also a service you can hear nothing about. The status page now says it out loud.
Actually verified, not merely declared
The check does not settle for confirming that a configuration exists. It queries the service for real and waits for its answer, exactly as we already do for the database. An expired or revoked access is therefore visible straight away, rather than at the first article that trips over it.
The call is a plain read, with no generation cost, and its answer is remembered for a minute: the page refreshes every thirty seconds without querying the service twice a minute per visitor.
Readable by outside monitoring
Like the other three checks, this one weighs on the response code: as soon as a service is degraded, /api/health answers 503 rather than 200. An external probe — yours, if you monitor your publishing chain — sees it on default settings, without having to parse the body. The /status page still shows which of the four services is affected.
What comes next
The fully European voice brick remains our current project. This version clears the ground: when the sovereign tier reads end to end in Europe, every link in that chain will already have its line on the status page.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo