Required confirmations before submitting
Issue Description
Description
When attempting to edit an existing alert, the Edit Alert page opens but none of the existing alert configuration is populated.
The page heading correctly displays "Edit Alert", but the form is completely blank and behaves as though a new alert is being created. This affects all sections, including:
- Alert type
- Included and excluded tenants
- Alerting script
- Schedule and first run time
- Notification actions
- Custom subject
- Alert comment
The Save Alert button remains disabled because the required fields have not been populated.
The same problem occurs when using Clone & Edit Alert, as the selected alert configuration is not loaded before cloning.
Steps to reproduce
- Go to Tenant Administration > Alert Configuration.
- Locate an existing alert.
- Select Edit Alert.
- Observe that the Edit Alert page opens, but all configuration fields are blank.
- Open browser Developer Tools and reload the Edit Alert page.
- Inspect the relevant Fetch/XHR request used to retrieve the selected alert.
- The request completes with HTTP status
200, but the response body is an empty array:
Environment Type
Sponsored (paying) user
Front End Version
v10.9.1
Back End Version
v10.9.1
Relevant Logs / Stack Trace
The Fetch/XHR request used to retrieve the existing alert completes successfully with HTTP status 200, but returns an empty array:
[]
Alert ID:
40f80655-276b-4ac8-bccd-de7d4314958a
Edit path:
/tenant/administration/alert-configuration/alert?id=40f80655-276b-4ac8-bccd-de7d4314958a
Clone path:
/tenant/administration/alert-configuration/alert?id=40f80655-276b-4ac8-bccd-de7d4314958a&clone=true
Browser Console contains no relevant application error.
The following browser warnings are visible but do not appear directly related:
- Fetch event handler is recognised as no-op.
- A form field element has neither an id nor a name attribute.
Hosting: CyberDrain-hosted
SKU: PremiumMV3
Runtime: Linux
Last update: v10.9.0 to v10.9.1 on 2026-08-24 15:57 UTC
Required confirmations before submitting
Issue Description
Description
When attempting to edit an existing alert, the Edit Alert page opens but none of the existing alert configuration is populated.
The page heading correctly displays "Edit Alert", but the form is completely blank and behaves as though a new alert is being created. This affects all sections, including:
The Save Alert button remains disabled because the required fields have not been populated.
The same problem occurs when using Clone & Edit Alert, as the selected alert configuration is not loaded before cloning.
Steps to reproduce
200, but the response body is an empty array:Environment Type
Sponsored (paying) user
Front End Version
v10.9.1
Back End Version
v10.9.1
Relevant Logs / Stack Trace