Troubleshooting

Lock refused or held by someone else

You tried to lock a resource and Lockit said no.

Someone else holds it

This is the most common reason. Lockit's reply names the holder and when their lock ends. You have three options:

1. Wait for it. Click Alert When Released and Lockit messages you when it's free.
2. Ask for it. Click Ask for Takeover. The holder can approve or reject.
3. Talk to them. If the lock looks forgotten, message the holder and ask them to release it.

See Alerts and takeovers.

The name doesn't match

Check the exact name with @Lockit list (Slack) or /lockit list (Discord). If the resource was renamed, the old name no longer works.

A refused lock through the API

The API answers a refused lock with HTTP 200 and a body that starts with Error:. Check the body in scripts, not just the status code. See Automate locks in CI.

Also check that:

• the API key has write scope (API keys)
• userEmail belongs to a member of your Slack workspace

Still stuck

Email hello@lockitbot.com with the resource name and the message Lockit sent.