You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It looks like statuspage bases notifications to subscribers based off incidents that are created. What if we do not have an incident created yet, but our automation triggers a status for one of our services to change and we want our subscribers to be notified right away before an incident is manually created?
Welcome to the community and thank you for your question regarding sending notifications out for component changes.
Unfortunately, we do not trigger notifications on component changes. It only sends notifications when there is an incident in play. The reason for this is because we want the most important things to trigger notifications and sometimes, especially with automation, component changes could cause a lot of notifications to go out and cause fatigue for the end user.
If you need to send notifications out to your customers, then we recommend having an incident go out. Hopefully that helps you out but please let me know if you have any additional questions. I hope you have a wonderful day!