Skip to main content

Menu

Sign In Register

Fix Integration And Channel Issues

Troubleshoot Apprentice integrations and channels across global setup, credentials, globally off state, per-agent subscriptions, wake settings, allowlists, and platform notes.

Fix Integration And Channel Issues

Integration issues can come from global setup, credentials, platform availability, per-agent subscriptions, wake settings, or runtime errors.

Start in Settings > External Communications, then check the agent's Channels tab.

Integration Missing

Open Settings > External Communications.

If the platform section says Coming soon, that integration is not currently available in the UI.

If the platform is available but no integration exists, select Add and configure credentials.

Credential Issue

The integration settings page can show credential problems such as:

  • Credential migration needed.
  • Credential migration failed.
  • Keychain unavailable.
  • Credential unavailable.
  • Credentials required.

Edit the integration and update credentials before testing again.

Integration Globally Off

If an integration is disabled globally, agents subscribed to it cannot use it normally.

Enable the integration in Settings > External Communications.

Use global disable when the whole integration should pause for maintenance.

Agent Not Responding

Open the agent, then Config > Channels.

Check:

  • The agent is subscribed to the integration.
  • The agent subscription is Active, not Paused.
  • Wake settings match the message you sent.
  • Channel allowlists include the channel or sender.
  • The agent provider and Docker runtime are healthy.

Wrong Channel Or Too Many Replies

Tighten per-agent channel settings.

Use allowed channel lists and narrow wake behavior. Start with mention-based behavior where possible.

If the agent responds too often, pause the subscription while adjusting settings.

Platform-Specific Notes

Signal uses a sidecar runtime. If Signal is stopped, start or restart it from External Communications.

WhatsApp uses linked-device behavior. Re-link if the session expires and prefer a dedicated number.

Twitch can require re-authorization if refresh fails repeatedly.

Email inbound requires IMAP or POP3 settings, not just SMTP.

Webhook and webhook modes are usually send-only and will not wake the agent from inbound messages.

Still Failing

Collect:

  • Integration type and mode.
  • Whether the integration is globally enabled.
  • Agent subscription state.
  • Wake settings.
  • Channel allowlist.
  • Integration log entry.
  • Run Detail error, if a run started.