Appearance
Troubleshooting Integrations
This page covers common integration issues for Sources, Scout Connectors, and API tokens.
I can’t create a Source
Symptoms
- You cannot open
AI System → Settings → Sources. - A Source type is gray in Add Source, with the tooltip "This source is not enabled. Please contact your administrator to enable it for your organization."
- Validation fails when saving a new Source.
- The Source saves, but doesn’t work.
Likely causes
- You are an AI System Editor or Viewer. These roles cannot open Settings.
- The Source type is off for your organization. Each type is off until an Organization Admin turns it on.
- Missing permissions in the service account.
- Invalid credentials.
- Network or allowlist constraints in your environment.
How to fix
- Ask an AI System Owner to add the Source.
- Ask an Organization Admin to turn on the Source type in
Organization → Source & Connectors → Sources. See Make a Source type available. - Use a dedicated service account with least privilege.
- Re-check credentials and required scopes.
- Try connecting with the minimum configuration first.
- If your environment requires allowlisting, contact Support to confirm what endpoints must be reachable.
Related: Sources
Scout Connector is disconnected or keeps expiring
Symptoms
- A Connector shows the status Expired or Disabled, or Scout can’t access content you expect.
- A Connector type is gray in Add Connector, and its tooltip tells you that the Connector is not enabled for your organization.
Likely causes
- Expired: your external session expired or was revoked.
- Disabled, or a gray type: an Organization Admin turned off the Connector type for the organization.
- Permissions changed in the external system.
How to fix
- For an Expired Connector, select the refresh icon in
User Settings → Connectorsto authorize it again. - For a Disabled Connector or a gray type, ask an Organization Admin to turn on the Connector type in
Organization → Source & Connectors → Connectors. - Confirm you can access the target content directly in the external system with the same account.
Related: Scout Connectors
My API token stopped working
Symptoms
- API calls fail with authentication errors.
- Modulos Client reports an authorization failure.
Likely causes
- The token expired.
- The token was revoked.
- The token is not being passed correctly.
How to fix
- Create a new token in
User Settings → API Tokensand rotate it in your integration. - Verify the token is stored as a secret and injected at runtime, not hard-coded.
Related: API Tokens, Modulos Client
When to contact Support
For integration issues, include:
- integration type, for example Datadog or GitHub
- whether it affects one user or the whole AI System
- any recent credential rotation or permission changes
- the timestamp and a screenshot of the error where possible