Caps 404 on connect

[adversinc]

Since we are using LMV now I'll ask here too instead of fighting this alone lol

Does someone experience caps seed 404 error while logging in multiple agents simultaneously? Around 10 at time. This started recently (December) and drives us nuts.

• XMLRPC returns a proper SeedCapability,
• LMV tries initialising Caps
• and SL region returns HTTP 404 with the following content:

cap not found: 'f91c296d-f824-a2fc-4aed-e2d7512e9602'

We had to implement the CapsError event to relog agent immediately, this seems to be working. I'll submit a detailed Jira bug after Christmas but curious if someone faces this too.

[cinderblocks]

I noticed the failure but have not had time to dive deeper. This is possibly related to all the changes they have been making with regards to the login service.