Troubleshooting the connectors generated with Connector forge

Use these solutions to help resolve problems that you might encounter while generating a connector with Connector forge.

Connectivity validation fails

Connectivity validation may fail when your credentials are not valid or you do not have sufficient permissions.

• Confirm that the credentials you provided are valid and not expired.
• Confirm that the credentials you provided have sufficient permissions to read data from the source.
• Confirm that the correct authentication method is selected for your data source. Note that the OAuth 2.0 is not supported.

AI coding agent produces unexpected output

Agent behavior may be inconsistent or incorrect if it is not configured to use Connector forge custom mode, or if the agent itself is not supported.

• Confirm that the agent is set to Connector Forge custom mode.
• Verify that you are using a supported AI coding agent (Claude Code or Bob).
• Check the GitHub repository for any updates to the custom mode or skill definitions that may address the issue.

Connector deployment fails

Depending on the chosen deployment method, try the following solutions:

• Serverless deployment: Confirm that your IBM Cloud or AWS account has the permissions required to provision serverless functions (Code Engine or Lambda).
• OpenShift automated deployment: Verify that the agent has API access to your OpenShift cluster and that the cluster has sufficient resources.
• Self-hosted server manual deployment: Review the instructions and deployment package provided by the agent. Ensure that the Docker image was built successfully before attempting to deploy.

Connector is not visible after registration

If you do not see your connector in the watsonx Connections UI after deployment, try the following solutions:

• Allow a few minutes for the registration to propagate.
• Refresh the Platform connections page.
• Confirm with your platform administrator that you have the permissions required to view connection assets.