Timeout while trying to fetch archived messages. Retry.

I get that a lot:

Clicking on it doesn't do shit :

changed milestone to %Previously done stuff

By Alexandre on 2020-01-16T13:33:05 (imported from GitLab project)

I see it occasionally especially when I do a refresh. We could increase the timeout period setting in Converse. See https://conversejs.org/docs/html/configuration.html#message-archiving-timeout

message_archiving_timeout¶ Default: 20000

The amount of time (in milliseconds) to wait when requesting archived messages from the XMPP server. Used in conjunction with message_archiving and in context of XEP-0313: Message Archive Management.

He he, might be a fix, yes.

By Alexandre on 2020-01-16T15:51:44 (imported from GitLab project)

added 1 deleted label

I got that error too a couple of times ! Looks blocking to me, why is the Priority tag blue instead of red ?

@balessan Not to be agressive

By Alexandre on 2020-01-22T16:14:54 (imported from GitLab project)

closed

By Alexandre on 2020-01-29T17:25:12 (imported from GitLab project)

removed 1 deleted label

@jbpasquier Coraline is experiencing this on Community. Is there a timeout we could increase again?

We can try, but I'm worried as default timeout is 20 seconds, more seconds needed could means that the user is disconnected or have problems with their internet connection or that we're experiencing an issue with our Prosody, all of those will not be solved by a higher timeout.

@jbpasquier I agree. What's the plan then: wait for store reactivity and analyze if it is better afterwards?