We have an ArcGIS Enterprise test environment in the cloud that we shut down nightly to save on costs. To manage this, I created a recurring ArcGIS Monitor Incident that stops monitoring the virtual machines (VMs) before the shutdown sequence begins and resumes monitoring after all VMs are fully online the next morning. This prevents alerts related to the shutdown and startup from being generated. The incident is configured to occur daily for 10 hours, starting at 10:00 PM.
The monitor server itself is included in the nightly shutdown. The incident begins before the server shuts down and ends well after it starts the next morning. However, after upgrading to ArcGIS Monitor 2024.1, I’ve noticed that the incident fails to transition from "active" to "queued". While stuck in the active state, I’ve found that temporarily changing the incident duration to 1 hour resolves the issue and queues the incident. Additionally, if the incident is set to begin after the monitor server is already offline, it queues correctly as scheduled after the server starts in the morning.
Has anyone else experienced this issue?
