Additional guidance provided here:

Yes, it is false for all tenants

Thank you

In your list of steps you don’t mention checking <tenantName>_mod_agreements.tenant_changelog_lock table. Can you confirm the locked column in this table is false

Also please confirm you have checked all the levels of lock table as listed by Ethan below? Can you let us know if any of these have lock entries ?

Only federation_lock table has entries. Typical process that we follow to get the module back up and running -

1. stop the container

2. Delete entries in federation_lock table

3. check if the system_changelog_lock table lock is set to true and if so, change it to false but in both cases, none of these were set to true

4. start the container and it operates fine again
   
   Main step was to delete entries from federation_lock table

We do not have a CPU allocation so the container can take as much CPU as needed from the underlying instance and each instance has typically 8 vCPUs - 8192 CPU to consume from