[BUG] future_initial_message isn't being sent when it should

redhat-performance / quads

:calendar: The infrastructure deployment time machine

https://quads.dev

GNU General Public License v3.0

88 stars 36 forks source link

[BUG] future_initial_message isn't being sent when it should #548

Closed sadsfae closed 3 weeks ago

sadsfae commented 3 weeks ago

It appears that future_initial_message is not being parsed and sent via postman.py when it should which should be immediately queued via next quads --notify run.

Instead it may appear later and batched with other notifications. This notification should be queued to send immediately.

sadsfae commented 3 weeks ago

This is actually caused by https://github.com/redhat-performance/quads/issues/546 which is now fixed.