When Claude goes wrong
Find the message Claude shows, then do what the table says.
Messages from FMS
| What you see | What to do |
|---|---|
| That email and password do not match a staff account. | Type them again. The console and Claude use the same password. |
| Too many sign-in attempts. Wait … seconds | Wait. Wrong passwords on the console count here too. |
| This staff account has been switched off. Ask an owner. | An owner switches you back on in Staff. |
| Your password is a temporary one | Sign in to the console, choose your own password on Your account, then connect Claude again. |
| This account still has the setup password | Ask an owner to set you a temporary password, then choose your own. |
| Set up two-step sign-in in the FMS console first | Sign in to the console and set it up on the screen it shows. See Two-step sign-in. Then connect Claude again. |
| That code is not right. | Type the newest code your authenticator app shows for FMS, or a recovery code. A code already used is refused too. |
| Type the code from your authenticator app, or one of your recovery codes. | The code field was empty. Type the code, then press Sign in and allow again. |
| Claude is switched off in this FMS environment (…) | The environment named in brackets has Claude switched off. Every environment starts off, production too. An owner turns it on under Sandboxes. |
| Claude cannot read this FMS environment (…) yet | Claude is switched on there, but its read-only database login is not ready for that database. Tell the technical team. |
| Too many questions in a short time | Wait the seconds it says, then ask again. This is the per-minute limit. |
| You have asked FMS a great many questions in the last hour | Wait the time shown, then ask narrower questions. The admin address was emailed. An owner can end the connection on Staff. |
| FMS withheld this answer | FMS stopped an answer that held data Claude may not see. Tell the technical team what you asked. |
| Your console role (…) does not include the decision board (or the risk board) | Your role cannot ask Claude about that board. Read it on the guide's project pages, or ask an owner. |
| A filter value is not recognised | Claude asked for a tier, status, kind or currency FMS does not have. Ask again with one of the values it lists. |
Claude says "Couldn't check the server", "Forbidden" or a 403
Claude could not reach FMS at all. It is not your account and not your password. Cloudflare sits in front of FMS and refused the call. The sign-in itself may still have worked, with every question failing after it: the sign-in page is outside the door, questions are not. Check these in order.
| Likely cause | What to do |
|---|---|
| The connector has no Request headers, or a value has a typo | Open the connector in Claude, add CF-Access-Client-Id and CF-Access-Client-Secret as an owner gave them to you, save, press Connect again. See Connect Claude |
| You connected before 5 October 2026 | Your connection has no Cloudflare values. Remove the connector and add it again with the headers |
| The yearly Cloudflare values have expired | Everyone fails at once. Ask the technical team for the new values, then type them into your connector |
| Claude's addresses are not on the Cloudflare list | Tell whoever runs the server. The fix is in the operations runbook under Cloudflare in front |
Claude cannot find the connector, or says FMS is not available
The connector may be switched off on the server, or the address is wrong. Copy it again from Your account. If Your account says the connector is switched off, only the technical team can turn it on.
Claude stopped answering after a password change
That is expected. A password change ends every Claude connection. See Disconnect Claude, then connect again.