[Bug]: Custom-sensor: alerts not sent for "warning". Critical works fine

[FabienD74]

Describe the bug

I have multiple "custom-senors".
Those at "warning" are not sent. the ones at "critical" work fine:

To reproduce

1. create a custom senor to trigger a warning
2. reboot pulse server.

Expected behavior

Receive the "Warning".

Additional actionable topics

None

Pulse version

V6.4.1

Agent version

v6.4.1

Image tag or digest

No response

Installation type

Bare metal / systemd

Relevant logs or diagnostics

N/A

Confirmations

• I verified the exact Pulse version and image reference from the running instance.
• I searched existing issues for duplicates.

[FabienD74]

OH, and it works fine if the "warning" happens while pulse-server is running....

[pulse-triage]

Confirmed and fixed on main in 3de3cd320d.

The custom-sensor warning path itself was correct. The loss was a startup ordering race: the monitor became available to agent-report handlers before Monitor.Start installed outbound alert callbacks. An agent reconnecting immediately after a Pulse restart could therefore create and persist the warning while no notification callback existed; a later warning worked because startup had finished by then.

External alert callbacks are now wired before the monitor is published. A regression test submits a warning custom-sensor observation before Monitor.Start and requires it to reach external delivery. This will be in the next release after v6.4.1; no agent configuration change is required.

How Pulse handles triage