Neil Marcellini

> we have the network's sequential queue here: > > https://github.com/Expensify/App/blob/ff423aa61fde128e981ee071b01011238927516c/src/libs/Network/SequentialQueue.js#L40-L44 > > which basically waits until the request is done including to process all middlewares, which includes writing to...

I think that [this issue](https://github.com/Expensify/App/issues/13586) with out of order messages when creating 2 bill splits while offline is another instance of this bug. Therefore, I'm going to hold it on...

Thanks! I'm actually going to have that issue closed soon, and the part where the messages are out of order will be fixed in https://github.com/Expensify/App/issues/13310. I'll update the description to...

I vote that we start working on a fix now. It feels like a liability to have a bug in one of our most common offline patterns.

I had an idea to ignore the Pusher update from the client that made the request. IIRC the Pusher updates that are sent back cause the problem. We should **confirm**...

> I don't think we can do that. The optimistic data is just that, the data we believe the server will return, but the server can (and will) return different...

I only had time for one small investigation, which was confirming that if you send two messages quickly on a slow connection then they will appear out of order when...

I never got around to creating that discussion, but I did do some more investigation. For the issue where messages are briefly out of order after going online, I confirmed...

> So we would be relying on something else re-fetching the correct data? Sounds a bit weird to me and kind of hard to determine, no? As far as I...

The name input on the workspace room settings page should be grayed out when there was an error updating it. I'll edit the issue description to make it more clear.