Delete Monitor
DELETE/api/EntityEventSchedules/DeleteMonitor/:id
Tier: Public — stable, supported for third-party integration.
Hard-deletes a schedule monitor, cascading its alert rows. On a known id the row is currently deleted successfully but the action still responds with a 400 (an internal result-code comparison defect), and the monitor's Hangfire recurring job is left registered against the now-deleted monitor (harmless no-op on each run, but not cleaned up).
Request
Responses
- 200
- 400
Not currently reached — an internal result-code comparison defect means even a successful delete responds 400.
No monitor with that id exists in the caller's organisation (NotFound); a known id currently also responds 400 with an empty error array despite the row being deleted.