Overnight failures
Maya Okafor, a data engineer at Acme Ltd, asked which runs failed overnight. Memtro listed the failed runs with their job and the schedule that launched them, and opened each to show which steps failed.
Dagster+ + Memtro
Which Dagster runs failed overnight, and when did our assets last update?
Dagster+ orchestrates your data pipelines. Memtro reads runs by job, status and date with steps succeeded and failed, code locations and their jobs, schedules and sensors and whether they are on, assets with their last materialization, and backfills. When asked and granted, it can launch, re-execute, terminate or delete runs, start or stop schedules and sensors, reload a code location, cancel a backfill, and report an external asset materialization or check result. The token acts with its user's role in each deployment, and each deployment is its own connection.
In Memtro
What you can do with Dagster+ in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dagster+ tool, reads what it needs, and answers with the source cited.
What it does
- 01List runs by job, status or date, with the partition, backfill, schedule or sensor that started each.
- 02Open one run's steps succeeded and failed, its materializations and the assets it targeted.
- 03See code locations and jobs, schedules and sensors and whether each is running, assets with their last materialization, and backfills.
- 04When asked and granted, launch a run or re-execute one from failure. It runs pipeline code against your systems and spends compute.
- 05When asked and granted, terminate or delete a run, start or stop a schedule or sensor, reload a code location, or cancel a backfill.
- 06When asked and granted, report an external asset materialization or check result, which can trigger downstream sensors or fire alerts.
Acts when asked
When you ask it to
These tools change something in Dagster+. 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.
- 01Launch a run of a job
- 02Re-execute a run (from failure or all steps)
- 03Terminate a run
- 04Delete a run's record
- 05Start a schedule
- 06Stop a schedule
- 07Start a sensor
- 08Stop a sensor
- 09Reload a code location
- 10Cancel a backfill
- 11Report an external asset materialization
- 12Report an external asset check result
In practice
Ask it like you would a colleague
Once Dagster+ 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.
Dagster+ + Memtro
Which Dagster runs failed overnight?
When was the orders_daily asset last materialized?
Which schedules are stopped right now?
How far has the March backfill got?
Re-execute last night's failed ingest run from failure.
Rerunning from failure
Tom Reilly, data platform lead at Northwind, asked Memtro to re-execute the failed ingest run once an upstream fix landed. Memtro started a new run from the failed steps, and the team saw it appear in Dagster+ beside the original.
Teams
Where it fits
The teams that lean on Dagster+ most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in Dagster+ 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.
- Work managementDagster+ with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementDagster+ with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementDagster+ with LinearIssues, projects and teams, synced hourly into memory.
- SupportDagster+ with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportDagster+ with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportDagster+ with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisDagster+ with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisDagster+ with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisDagster+ with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withUser token and organization
- 1
In Dagster+, open Organization Settings → Tokens and create a user token, ideally for a service user with only the role Memtro needs. Click Reveal token and copy it.
- 2
In Memtro, open Connections → Dagster+ and paste the User token and the Organization, such as acme from acme.dagster.cloud.
- 3
Set the Deployment, such as prod, and the Domain if your address uses dagster.plus. An administrator grants the run, schedule and sensor actions by name to the teams that may use them.
- 4
Ask which Dagster runs failed overnight.
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dagster+ tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Dagster+?+
Only when you ask, and only what it has been granted: launch a run of a job; re-execute a run (from failure or all steps); terminate a run; delete a run's record; start a schedule; stop a schedule; start a sensor; stop a sensor; reload a code location; cancel a backfill; report an external asset materialization; report an external asset check result. 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.
Who can use a Dagster+ connection?+
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.
Does Memtro store my Dagster+ data?+
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.
How do I connect Dagster+?+
User token and organization. In Dagster+, open Organization Settings → Tokens and create a user token, ideally for a service user with only the role Memtro needs. Click Reveal token and copy it.
Connect Dagster+ in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.