Automated Appwrite Function Failure Triage
Every morning, WebRun opens Appwrite, walks the executions list for every function across your projects, separates the runs that failed overnight, pulls the error out of each log, posts a grouped triage list to Microsoft Teams, and pings the on-duty developer in Telegram.
How do I triage Appwrite function executions that failed overnight?
Every morning, WebRun opens Appwrite, reads the executions list for each function across your projects, and separates the runs that failed overnight from the rest. It pulls the error from each failing execution's log, posts a grouped triage list to Microsoft Teams, and pings the on-duty developer in Telegram.
- Failing functions and their errors are grouped before standup
- Repeat failures are reported once, not hundreds of times
- Nothing is retried or redeployed without a developer deciding
Built for backend developers · on-call engineers · startup engineering teams · indie app builders
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
cloud.appwrite.ioin a real browser with your saved login - no setup, no API keys. -
1
Appwrite - find overnight failed executions
appwrite.io
WebRun opens Appwrite to find overnight failed executions. - Open Appwrite and select each project you want covered
- Go to Functions and open the executions list for each function
- Filter to executions from the last twelve hours and separate the failed status from the rest
- Open the log on each failed execution and capture the error and the duration
Done when Every overnight failed execution is captured with its function, project and error.
-
2
Microsoft Teams - post the triage list
microsoft.com
WebRun opens Microsoft Teams to post the triage list. - Post the triage list to your engineering channel
- Group the failures by function, with a count and the shared error at the top of each group
- Put functions that failed every run above functions that failed once
- Note any function that ran clean all night, so the list is not read as the whole picture
Done when The channel has this morning's failures grouped by function with their errors.
-
3
Telegram - ping the developer on duty
telegram.org
WebRun opens Telegram to ping the developer on duty. - Send the developer on duty a one-line summary with the failure count
- Name the worst function first and link back to the Teams post
- Stay quiet on a morning when nothing failed
Done when The on-duty developer knows the overnight state before opening the console.
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
Will it redeploy or retry anything?
No. WebRun only reads executions and logs. Retrying a function, changing code or redeploying stays a human action inside Appwrite.
Does it cover every project?
Yes, every project you list. WebRun opens the Functions executions list in each one, so a failure in a side project is not missed.
What if the same function fails hundreds of times?
It is reported once, as a group with the run count and the shared error, so the list stays readable instead of flooding the channel.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.