Troubleshooting and FAQ

BETA

Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.

Use this page for connection, authentication, and access issues with the Relewise plugin, MCP, or REST API.

The Plugin, Skills, or MCP Tools Do Not Appear

After installing a plugin or adding an MCP connection, restart your AI client if the plugin, its skills, or MCP tools do not appear. Some clients only load them when starting.

If they are still unavailable, confirm that the plugin or MCP connection is enabled and that installation or connection setup completed successfully.

The Token Is Missing or Rejected

A 401 Unauthorized response means the request could not authenticate. For a Personal Access Token, check that it is active and has not expired or been revoked. For OAuth, reconnect the Connected App if its session was revoked or disconnected.

• OAuth: Follow your client's sign-in flow to reconnect through Connected Apps. For the Relewise plugin, ask the assistant to help you reconnect.
• Personal Access Token: Confirm that the token is available through your client's configured credential storage. If the plugin uses RELEWISE_AGENT_GATEWAY_TOKEN, check that the AI client can read it and restart the client after changing a persistent environment variable.

For MCP and REST requests, the client sends Authorization: Bearer <token>, where <token> is an OAuth access token or Personal Access Token.

If you lost or regenerated a Personal Access Token, update the client's stored credential. Never paste the token into chat. See Personal Access Tokens for regeneration and expiration settings.

No Datasets Are Visible

Successful authentication does not guarantee that any Datasets are available. Confirm that your My Relewise user has access to the expected Dataset and that the Connected App's Dataset access or the Personal Access Token's Dataset Scope includes it.

For MCP, call get_me to list available Datasets. For REST, use the Identity endpoint. If the Dataset appears but a request fails, check the permissions and settings below.

A Capability Is Unavailable or Access Is Denied

Check the Dataset you selected and its settings in Administration > Agent Gateway:

1. Your user must have Use Agent Gateway permission. Administrators have this access by default.
2. The Connected App's Dataset access or the Personal Access Token's Dataset Scope must include the Dataset.
3. Enable the Connection Method your client uses: MCP for MCP connections or REST API for REST connections.
4. Enable the Allowed Area needed for the operation.

If you cannot change these settings, ask your Administrator. Use the error message and Request Logs to identify the missing permission or setting. See Security and Permissions for access requirements.

The Dataset Cannot Be Found

Check the Dataset ID in the REST URL or the MCP tool's datasetId argument. Use an ID returned for your user and token rather than guessing or copying one from an example. See Dataset selection for MCP or REST.

The Request Does Not Appear in Request Logs

Requests with missing, invalid, expired, or revoked tokens do not appear in Agent Gateway Request Logs. Start with token troubleshooting.

Also check that your client uses the correct endpoint in the MCP or REST guide. See Request Logs for where to find logged requests.

Can I Use a Dataset API Key?

Agent Gateway uses an OAuth access token from a Connected App or a Personal Access Token associated with your My Relewise user. A Dataset API Key is not a substitute.

Do I Need a Connection for Each Dataset?

One MCP connection can work with multiple Datasets. Pass the selected datasetId with each tool call that requires it. Your token and user must have the necessary access to each Dataset.

The Relewise plugin discovers available Datasets during setup. REST integrations select a Dataset in the URL when the endpoint requires one.

Why Am I Only Getting Some Results?

Some lists return one page at a time. Follow the response's pagination metadata using page-number pagination, or follow the cursors for Administration execution history.

Entity searches and details have separate result limits. Entity searches return at most 25 results; detail responses can also limit Data Values and Variant summaries. Use the documented truncation flags and detail operations when inspecting those responses.

The Client Is Sending Too Many Requests

Reduce the request frequency and retry later when a request is rate-limited. See Request Throttling.

Still Need Help?

Contact Relewise Support with the client you use, the operation, the Dataset ID, and the error message or relevant request log. Do not include your token or other credentials.

For broader product questions, see the Relewise FAQ. For Search behavior in My Relewise, see Troubleshoot in My Relewise.