Troubleshoot

This page lists common errors and known issues encountered while integrating Cursor with Zluri, along with steps to resolve them.

CURSOR-100-A: The API token used to connect this integration is invalid

When this error occurs

This error occurs when the API token used to connect Cursor to Zluri is invalid or incorrectly copied.

How to resolve

  1. Verify the API token

    • Copy the entire API token without extra spaces or missing characters.
    • Ensure the token does not contain unintended line breaks or formatting.
    • Paste the API token exactly as generated.
  2. Generate a new API token if required

    1. Sign in to Cursor.
    2. Go to SettingsAPI Keys.
    3. Select Create API Key.
    4. Enter a meaningful description for the API token.
    5. Copy the generated API token immediately.
  3. Reconnect the integration

    • Reconnect the Cursor integration in Zluri using the valid API token.

CURSOR-100-B: The API token used for this integration is expired or revoked

When this error occurs

This error occurs when the API token used to connect Cursor to Zluri is revoked or inactive.

How to resolve

  1. Verify the API token status

    • Sign in to Cursor.
    • Go to SettingsAPI Keys.
    • Confirm that the API token used for the Zluri integration is still listed and active.
  2. Generate a new API token if required

    • Generate a new API token if the existing token is missing, revoked, or inactive.
    • Copy the generated API token immediately.
  3. Reconnect the integration

    • Reconnect the Cursor integration in Zluri using the new API token.

CURSOR-101-A: Insufficient permissions to access team members

When this error occurs

This error occurs when the API token does not have permission to retrieve team member data through the Cursor Admin API.

How to resolve

  1. Verify the account permissions

    • Confirm that the account associated with the API token has Administrator access in Cursor.
  2. Verify the API token permissions

    • Confirm that the API token can access the required Admin API endpoints.
    • Ensure the API token can retrieve team member data.
  3. Generate a new API token if required

    • Generate a new API token using an account with Administrator permissions.
  4. Reconnect the integration

    • Reconnect the Cursor integration in Zluri using the new API token.

CURSOR-101-B: Permissions to access team member data were revoked after connection

When this error occurs

This error occurs when the permissions associated with the API token were reduced or revoked after the integration was connected.

How to resolve

  1. Review the API token permissions

    • Sign in to Cursor.
    • Go to SettingsAPI Keys.
    • Review the permissions assigned to the API token used for the Zluri integration.
    • Confirm that the API token can access the required Admin API endpoints and retrieve team member data.
  2. Restore the required permissions

    • Restore the API token permissions if they were changed or revoked.
  3. Generate a new API token if required

    • Generate a new API token with the required permissions if you cannot restore the existing permissions.
  4. Reconnect the integration

    • Reconnect the Cursor integration in Zluri using the updated API token.

CURSOR-102-A: No users found in the Cursor account

When this error occurs

This error occurs when Zluri connects to Cursor successfully but Cursor returns no team member data.

How to resolve

  1. Verify that team members exist

    • Confirm that the Cursor workspace contains one or more team members.
    • Ensure the team members are active.
  2. Verify the connected account

    • Confirm that the API token is associated with the correct team or account.
    • Confirm that the integration is connected to the correct organization or workspace.
  3. Verify API access

    • Confirm that the API token can retrieve team member data through the Cursor Admin API.
  4. Review additional resources

    • If team members exist but the issue persists, review the Cursor Admin API documentation or contact your Cursor administrator.

If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].



Did this page help you?