Overnight failures
Sarah Chen, data engineer at Acme Ltd, asked which runs failed overnight. Memtro listed the failed jobs with path, schedule and error message, and the schedules showing the same last error. She fixed the script that morning.
Which Windmill runs failed overnight, and what error did each give?
Windmill connects Memtro to your workflow engine, in the cloud or self-hosted. It reads recent runs with their state, duration and, for failures, the error, plus queued, running and suspended jobs and any one job. It reads scripts, flows and schedules with their cron, timezone, target and last error. When asked and granted, it can run a script or flow now or later, cancel a job, resume or restart a flow, create, enable, disable or delete a schedule, and archive a script or flow. Arguments, results, logs and code are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Windmill tool, reads what it needs, and answers with the source cited.
These tools change something in Windmill. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Windmill is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which runs failed overnight, and why?
Which flows are suspended waiting for approval?
Which schedules have a last error?
What inputs does the invoice sync flow take?
Disable the nightly export schedule.
Sarah Chen, data engineer at Acme Ltd, asked which runs failed overnight. Memtro listed the failed jobs with path, schedule and error message, and the schedules showing the same last error. She fixed the script that morning.
Dan Fletcher, finance lead at Northwind, asked Memtro to approve the payment run flow waiting at its approval step. With the action granted, Memtro resumed the suspended flow as its owner, and its remaining steps ran. The run then appeared among Windmill's completed jobs.
The teams that lean on Windmill most, a question each of them asks, and what they connect beside it.
A record in Windmill is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Windmill, open your user menu, then Account settings, then Tokens, and create a token. Tick Limit token permissions and give it the read scopes, plus run, cancel or schedule scopes only if Memtro should act.
In Memtro, open Connections → Windmill and paste the Workspace id from the /w/ address and the Token. Set Host and Port only for a self-hosted instance.
An administrator grants the run, schedule and archive actions by name to the teams that may use them, since a run executes your own code.
Ask which runs failed overnight and why.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Windmill tools are the same everywhere.
Only when you ask, and only what it has been granted: run a script (now or at a set time); run a flow (now or at a set time); cancel a queued or running job; resume a suspended flow as its owner; restart a completed flow from a step; create a schedule; enable or disable a schedule; delete a schedule; archive a script; archive or unarchive a flow. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Workspace and token. In Windmill, open your user menu, then Account settings, then Tokens, and create a token. Tick Limit token permissions and give it the read scopes, plus run, cancel or schedule scopes only if Memtro should act.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time