---
title: "Troubleshoot Integration Hub"
canonical: "https://help.agiloft.com/space/HELP/598540631/Troubleshoot+Integration+Hub"
format: markdown
---
Use this article to troubleshoot Integration Hub connections and recipe errors.

# Connection issues

During the initial Integration Hub [setup](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/597688481), an Agiloft CLM connector is created automatically. You can use that connection in all of the recipes that sync data with your KB. This article provides guidance on reconnecting the connector when it’s disconnected. It also includes instructions on creating a new connection from scratch if you need to.

For information on creating connectors for other applications, see Workato’s documentation on [connections](https://docs.workato.com/en/connections.html#connection-basics) and [connectors](https://docs.workato.com/en/connectors.html).

> ℹ️ **Best practice**
> ℹ️ 
> ℹ️ For connector authentication and access token management, your KB should have a separate integration service user account set up with an admin license. Associate any connector-related OAuth clients with this user account and make sure you supply this user’s credentials when authenticating the connection. For information on creating user records, see [User Management](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/926744591).

## Reconnect a lost connection

If the Agiloft connection is lost, it’s typically because the OAuth token expired and needs to be reauthorized. To repair the connection:

1. In Integration Hub, go to App Connections.
2. Click the Agiloft connection.
3. At the bottom of the screen, click Disconnect.
4. Now click Connect. You are prompted to log in.
5. Enter the credentials for the integration user account and click OK, then click Allow Access. The connection is restored.

If the connector is disconnected with an `Unable to grant access. Customer setting is invalid: invalid_request` error message, it may mean the OAuth 2.0 client application is disabled. To check and enable it if necessary:

1. Go to **Setup > Integration > OAuth2 Client Setup**.
2. In the list of clients, check the Status for the Integration Hub client. The system-generated client is named “Config for Agiloft OAuth 2.0 Workato connector.” If the status is Enabled, it’s not the issue. If it’s Disabled, go to the next step.
3. Click the profile to open the configuration.
4. At the bottom of the screen, click Enable.
5. Return to the connection in the Integration Hub and click Connect, then follow the prompts to log in as the integration user and allow access. The connection is restored.

## Resolve authorization errors

An `Unable to grant access. Request is out of date or blocked: invalid_request` error message may mean the wrong credentials were used to authorize the connection. To resolve the issue:

1. In the connection configuration, click Disconnect if it’s available.
2. Now click Connect and follow the prompts to log in as the integration user and allow access.

## Create a new connection

You don’t typically need to create Agiloft CLM connections from scratch because the connector created during Integration Hub setup can be used in all of your integrations. If Support recommends you start over with a new connection, you can follow the steps below to create one.

1. First, create an OAuth 2.0 client application in your KB:
  1. Log in to your KB as an administrator.
  2. Go to **Setup > Integration > OAuth2 Client Setup**.
  3. Click New to create a client.
  4. In the client configuration, leave Authorization Code selected as the Authorization Grant Type.
  5. Next, give the client a Name and Display Name. Name is the name the application uses with the REST API, and Display Name is the name that appears in the KB.
  6. In the Full Name field, select the integration user account. Selecting the user automatically populates the Associate this Application with Contact ID field with the user ID.
  7. In the Redirect URI field, add this URI: `https://www.workato.com/oauth/callback`
  8. Set the Token Expiry in Minutes field to the number of minutes the access token should remain valid before expiring. The default value is 15. Valid values are 1 to 60.
  9. Now, click Save to save the configuration.
  10. Scroll to the bottom of the screen and click Enable. The system generates a Client ID and Client Secret for the application.
  11. Copy the Contact ID, Client ID, and Client Secret values to an accessible location where you can access them in the next step.
2. Now, create the connection in Workato and connect it to your KB:
  1. In Workato, go to Projects, then go to Connections.
  2. Click Create and select Connection.
  3. Search for Agiloft and click the Agiloft connector in the results. The Connect to Agiloft screen is displayed.
  4. Give the connection a Name.
  5. In the Location field, select the project where you want to store the connection.
  6. In Connection Type, leave Cloud selected.
  7. Under Subdomain, click Define subdomain and select Use custom URL. Then enter the base URL for your KB. Make sure you remove any trailing slashes (/). For example: `https://example.agiloft.com`
  8. In Knowledgebase, enter your KB name.
  9. Add the Contact ID, Client ID, and Client Secret values that you copied from the OAuth client configuration.
  10. Select the Language if needed and then click Connect. You are prompted to authenticate the connection.
  11. Supply the credentials for the integration service account user and click OK, then click Allow Access.

The new connection is now connected to your KB.

# Recipe errors

## Events per poll limit reached

**Error**: Events per poll limit reached: Your recipe was stopped because it exceeded the limit of 1000 events in a single poll.

**Solution**: Update the Agiloft connector by stopping the recipe and then starting it again.

#### Related articles

> Macro (contentbylabel)