Cannot schedule future alarms as they are firing immediately

[flashdagger]

When sending alarms via the API I set the startAt timestamp greater than the current timestamp.
I was expecting they got fired after the set time. This way I wanted to implement a dead man's switch for my application, which would always postpone the alarm by updating the startAt timestamp. In case the application crashes, the alarm would finally fire after the last updated time.

This is apparently not the case as the alarm fires immediately (or within group_wait time).
Is this intended behavior?

[grobinson-grafana]

That's correct. You cannot create alerts in the future with a startsAt timestamp newer than the current time.

[flashdagger]

Thanks for the reply.