[Bug]: Alert configurations edited via dynamic configurations are not synced with Cloud until an alert transition occurs

[car12o]

Bug description

Alert configurations edited through dynamic configurations on the Agent are not immediately synced with the Cloud. The current implementation only triggers configuration sync when an alert transition (escalation/de-escalation) occurs, not when the configuration itself is modified.

Expected behavior

When a user edits an alert configuration through dynamic configurations:

1. The configuration change should be detected and synced to Cloud proactively (not waiting for an alert transition)
2. Cloud should always have the most up-to-date configuration for any alert, regardless of whether that alert has recently transitioned

Steps to reproduce

Steps to Reproduce:

1. Set up a Netdata Agent connected to Netdata Cloud
2. Identify an existing alert with a known configuration
3. Verify the alert configuration is visible in Cloud
4. Edit the alert config through dynamic configurations (e.g., change warning/critical thresholds, summary, etc)
5. Observe that the configuration in Cloud does not update
6. Wait for the alert to transition (trigger the alert condition)
7. Only after the transition does Cloud receive the updated configuration

Screenshots

No response

Error Logs

No response

Desktop

OS: Archlinux
Browser: Brave
Browser Version: v1.86.146 (Jan 28, 2026)

Additional context

No response

[stelfrag]

This netdata/netdata#21706 will attempt to improve this without generating too much traffic.

[stelfrag]

This has been merged, it will available in the next nightly