We have a subscription set up to send a notification to a webhook, for deployment events in the UAT or Production environments for specific project groups.
We had a deploy today for a project in one of those groups, to UAT, but the subscription did not fire:
The deployment in question was AutoId 1186995. We did get a notification for 1186996.
(I cut down the columns for size, but can provide more of the data if needed.)
Redeploying the release did send a notification as expected.
The only thing I can come up with is if there was some sort of race condition - the Occurred stamp in the Event table for that event was 2020-09-02 16:30:36.6260747 +00:00, or the exact same time (once you take time zones into consideration - the log screenshot is in Eastern Daylight Time) as it decided that “no notifications need to be sent”. If the Event is not written to the table in a single step, and the subscription engine read the record partway through, that could explain why the subscription rules didn’t pick it up…
We are still on Octopus v2019.12.8 - waiting for a new SQL server to be built so we can upgrade. However, I don’t see anything in the release notes for later versions that seems to be related.