Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
sadsfae opened this issue Nov 5, 2024 · 1 comment
Closed

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

sadsfae opened this issue Nov 5, 2024 · 1 comment
Assignees
@sadsfae
Labels
bug notifications quads-tools
Milestone
2.x Series - Bowie

Comments

@sadsfae
Copy link
Member

sadsfae commented Nov 5, 2024

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 sadsfae added this to the 2.x Series - Bowie milestone Nov 5, 2024
@sadsfae
Copy link
Member Author

sadsfae commented Nov 5, 2024

This is actually caused by #546 which is now fixed.

@sadsfae sadsfae closed this as completed Nov 5, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in QUADS 2.1 Series Nov 5, 2024
@sadsfae sadsfae self-assigned this Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sadsfae sadsfae

Labels
bug notifications quads-tools
Projects
QUADS 2.1 Series
Status: Done
Milestone
2.x Series - Bowie
Development

No branches or pull requests
1 participant
@sadsfae