DocsMonitoring and alerts
What alerts say
Every alert says what happened in plain words, gives the key facts, and offers one action link. It never contains your data rows: only counts and messages Ladeworks wrote.
What is in an alert
- A headline, such as "Daily returns report failed" or "Daily returns report finished with 9 rows skipped".
- Facts, such as What happened, Result and Usage ("9 API calls"). A failure also says what was sent: "Nothing was sent to Kestrel Shop API. Your data is unchanged."
- One action link: Open the run, See skipped rows, Reconnect and the integration's name, Review the change, See usage, Raise spending cap or Open the workflow.
Rows skipped alerts list up to three skipped rows with their messages, but only for people who can see payloads. Everyone else gets "Open the run to see why." because a message can quote values from your data.
Which alerts exist
| Event | Subject line | Who gets it |
|---|---|---|
| A run fails | Run failed: <workflow> | People who follow it, and the owner when nobody does |
| A run ends early | Run ended early: <workflow> | Followers |
| Rows are skipped | <workflow>: 9 rows skipped | Followers |
| A run succeeds | Run finished: <workflow> | Followers |
| An integration needs reconnecting | <integration> needs to be reconnected | Followers of the workflows that use it, and Owners and Admins |
| An API change is found | A change in <integration>: <change> | Followers of the affected workflows, and Owners and Admins |
| Usage is high | You've used 80% of your API calls, and Your spending cap was reached and workflows are paused | People who can see billing |
| Someone edits a workflow I follow | <person> changed <workflow> | Followers, except the person who edited |
Each person still needs the event switched on in their notification settings. The 80% alert is sent once a month, and the spending cap alert once a month, always right away. Both say when calls reset, and the 80% alert adds a forecast and a tip to batch your biggest workflow. See Usage and the spending cap.
By email, Slack and Discord
- Email. A headline, a box of facts, one teal button and a footer.
- Slack. A bold title, a few short lines and a button for each action link, in a message with a colored bar and the footer "Ladeworks" and the workspace name.
- Discord. The same content as an embed. A Discord webhook cannot carry buttons, so the links are written into the text. Alerts never mention anyone.
The colored bar shows how urgent it is: coral for a problem that needs you (a failed run, skipped rows, a reconnect, a spending cap reached, an API change that needs action), amber for a warning (a run that ended early, a heads up, 80% of calls used) and teal for good news or information.
The email footer
Every alert email ends with a line that says why you got it, and a link to change it. The reasons are:
- "You get this because you follow <workflow>."
- "You get this because you own <workflow> and nobody follows it."
- "You get this because you are an Owner of <workspace>." (or an Admin, for reconnect and API change alerts, and a billing role for usage alerts)
Change your alerts opens your notification settings. The daily summary email lists each alert with its action link, and its footer says "You get one summary a day at 8:00 AM because your delivery is set to a daily summary. Failures and reconnect alerts still come right away."