> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paraform.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fix sign-in, access, and tool errors when you use Paraform in your AI assistant.

Find the message you see, then follow the fix. If a problem continues, see [Get help](#get-help).

## Sign-in and access

Your assistant can show these messages when it connects to Paraform.

| Message | What to do |
| - | - |
| A message that this account has no MCP access | The Paraform account you signed in with can't use the connector. Disconnect, then sign in with the right account. |
| This sign-in is no longer valid. Sign in again. | The sign-in expired, or access was removed. Most assistants ask you to sign in again on their own. If yours doesn't, disconnect Paraform in your assistant's connector or MCP settings, then connect again. |
| `access_denied` | You declined the consent screen. Connect again and select **Allow**. |
| Paraform could not confirm this sign-in in time. Please retry in a moment. | Wait a few seconds, then try again. You can also see this when you reach the [request limit](#request-limit). If it continues, contact Paraform with the request ID. |

## Tool errors

When a tool fails, the assistant gets a short error with a status code, the reason, and a request ID. Include the request ID when you contact Paraform. If Paraform doesn't answer in time, the error says `did not respond within 60000ms` and has no status code. Try again once. If it repeats, send the request ID to Paraform.

| Status | What to do |
| - | - |
| `400` | A filter value isn't valid, for example a location Paraform doesn't recognize. The error lists the accepted values, so the assistant can retry. If it doesn't, ask again in plainer words. |
| `403` | The message says `This account cannot see this resource.` Ask for access to it in the Paraform app. Retrying doesn't help. If every request fails this way, reconnect. |
| `404` | The item doesn't exist, or you can't see it. The message says `List again to get a valid id.` Ask the assistant to search again by name. |
| `429` | You reached the [request limit](#request-limit). The message says `Rate limit exceeded (retry after N seconds)`. Wait that many seconds, then try again. Ask narrower questions instead of asking the assistant to loop over many items. If the message starts with `Too many concurrent requests`, too many tool calls ran at once. Ask the assistant to work one item at a time. |
| `5xx` | A temporary Paraform error. Try again once. If it repeats, send the request ID to Paraform. |

### Request limit

Limits apply per account, per minute and per week. Each kind of tool has its own limits, so heavy use of one kind doesn't block the others. Weekly limits reset Sunday 00:00 UTC.

| Tools | Per minute | Per week |
| - | - | - |
| Searches, lists and quick lookups: `getNewRoles`, `getMyCandidates`, `getRolesForCandidates`, `getParascribeCalls`, `getMyEarnings`, `getMyRoleLists`, `getQnA`, `aboutMe`, `getMyRoles`, `getMyAllowances`, `getRecruiterCompanies`, `getRecruiterPreferences`, and every hiring manager tool | 180 | 15,000 |
| Detailed reads: `getRecruiterRoles`, `getCandidateRoleEligibilities`, `getCandidatesForRole` | 120 | 7,500 |
| Changes: `manageCandidates`, `manageSubmissions`, `manageMyRoleLists`, `submitFeedback` | 10 | 5,000 |
| Calibration: `getCandidateRoleCalibration` | 5 | 250 |
| Submitting: `finalizeSubmission` | 1 | 20 |

A submission takes two `finalizeSubmission` calls, a preview and a confirm, so the confirm waits a minute after the preview and a week allows about 10 submissions.

Sign-in checks, `getIdentity` and `getToolChanges` have their own limits of 60 per minute and 10,000 per week, and don't count against tool limits. Past a limit, those requests fail until it resets: the message says `Weekly rate limit exceeded` for a weekly limit, with the seconds left until Sunday.

Paraform also limits how many of your tool calls run at the same time. When about 4 of your calls are still running, another call can fail with `Too many concurrent requests; wait for in-flight calls to finish before sending more`. Let the running calls finish, then try again. A refused call still counts toward your per-minute and weekly limits, so don't retry it in a loop.

## Other problems

**The assistant doesn't use Paraform.** Make sure the connector is on for this chat. In ChatGPT, start the message with `@Paraform`. Mention Paraform in your question.

**A tool is missing or out of date.** Your assistant may still use the tool list from when you connected. Refresh the connector's tools, or disconnect and add Paraform again. You can also ask the assistant what changed in Paraform's tools. See [Keep tools up to date](https://docs.paraform.com/mcp/connect.md#keep-tools-up-to-date).

**A list looks short.** Lists return one page at a time. Ask the assistant for the next page.

## Get help

Email [team@paraform.com](mailto:team@paraform.com). Include the request ID from the error if there is one. See [Get help](https://docs.paraform.com/support.md) for more.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.