Automated Stitch Replication Failure Log
Every morning, WebRun opens Stitch, checks every integration's last replication run, logs any failed or errored job to Airtable with its table and error, and writes a short runbook summary into Notion so the on-call engineer knows where to start.
How do I catch failed Stitch replication jobs early?
WebRun checks every Stitch integration's last replication run each morning, logs any failed table to Airtable with its error, and writes a runbook summary in Notion for whoever picks it up. Data engineering teams catch a broken replication job before a downstream table goes stale, with the error already written down.
- A failed replication job is logged before a report goes stale
- The on-call engineer starts with a written runbook, not a blank dashboard
- Unresolved failures stay tracked instead of repeating as new
Built for data engineering teams · analytics engineers · data ops teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.stitchdata.comin a real browser with your saved login - no setup, no API keys. -
1
Stitch - check replication runs
- Open Stitch and check the last run of every integration
- Read the status of each replicated table
- Note the table, the error, and the time for anything that failed
Done when Every integration's last run status is checked.
-
2
Airtable - log the failures
airtable.com
WebRun opens Airtable to log the failures. - Open the pipeline failures base in Airtable
- Log a row for each failed table with its error and integration name
- Mark whether it's a new failure or one still unresolved from before
Done when Every failed table today is logged with its error.
-
3
Notion - write the runbook summary
notion.so
WebRun opens Notion to write the runbook summary. - Open the on-call runbook page in Notion
- Summarize which integrations failed and what the errors suggest
- Link to the Airtable log for the full detail
Done when The runbook page reflects today's failures.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun restart the failed replication job?
No. It only reads job status and logs the failure. Restarting a job or fixing a source schema stays a manual step.
Will an old unresolved failure get logged again every day?
It stays marked as still unresolved rather than logged as brand new, so the Airtable history doesn't inflate the count.
Does it read the actual replicated data?
No. It only reads job status and error messages from Stitch, not the row level data being replicated.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.