We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
From #1234 (comment)
The idea behind the messaging feature is that it ought to work mostly in realtime, while still supporting async communication.
In order to achieve that, we need to be able to send an email to the user if the message sent to them has not been marked as read after 3 minutes.
The text was updated successfully, but these errors were encountered:
What needs clarification here?
Sorry, something went wrong.
Possibly the best way to do this is check and see whether an email was sent every so often by looping through unread messages in Quantum every minute.
I saw this article recently: https://medium.com/@efexen/periodic-tasks-with-elixir-5d9050bcbdb3?utm_content=buffer2ea59&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
@snewcomer we've used this to great success in other projects https://github.com/c-rack/quantum-elixir
No branches or pull requests
Problem
From #1234 (comment)
The idea behind the messaging feature is that it ought to work mostly in realtime, while still supporting async communication.
In order to achieve that, we need to be able to send an email to the user if the message sent to them has not been marked as read after 3 minutes.
The text was updated successfully, but these errors were encountered: