Message queuing doesn’t retry when your connectivity changes #3152
Labels
A-Message-Queueing
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
Comments
Velin92
added
S-Major
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Outcome
What did you expect?
The act of changing network (or spotting other traffic is successfully sending) should kick the retry mechanism into doing another retry immediately
What happened instead?
It seems to ignore network connectivity state and waits for the next retry timeout.
Your phone model
No response
Operating system version
No response
Application version
675
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: