Feature
Automation you can actually see running
Automated workflows are only trustworthy if you can see them working. Meridian's workflow observability page shows run history and status for every system workflow — PPM scheduling, SLA watching, compliance and document expiry sweeps — so 'is this actually running?' has an answer.
The problem
Automation that runs silently in the background is indistinguishable from automation that's silently broken, until something that should have fired doesn't.
Why it matters
A PPM cycle that should have generated a ticket, or an expiry sweep that should have flagged a lapsing Ejari, is only useful if someone can confirm it actually ran — otherwise automation just moves the point of failure somewhere less visible.
How Meridian helps
- A dedicated workflows view showing run history and status for every system workflow
- Coverage of the core scheduled workflows — PPM scheduling, SLA watching, compliance and document expiry sweeps
- Each run's outcome visible, so a stalled or failed run is flagged rather than silently skipped
- Confidence that automated reminders and ticket generation are actually firing, not just configured to
Workflow example
- 1A PPM cycle comes due for a building
- 2The scheduling workflow runs and generates the maintenance ticket automatically
- 3The run is logged with its status on the workflows page
- 4A team member can check the page at any time to confirm the cycle actually fired, rather than assuming it did
FAQ
What workflows does this cover?
System workflows including PPM scheduling, SLA watching and compliance/document expiry sweeps are tracked with run history and status.
Can I see why a specific run happened or didn't?
Each logged run shows its status, so a run that didn't fire as expected is visible rather than assumed to have happened.