Troubleshoot integrations and tools

When a persona cannot use a service, check the saved connection, the persona assignment, and the requested action in that order.

1. Open the saved connection

Open Integrations and choose the service. Read the message beside Needs attention, Disconnected, or the service’s receive status.

Follow the named repair action. Depending on the service, that can mean reconnecting an account, updating a token, granting a missing permission, or finishing setup. Use the service’s credential fields for updates.

Check that the connected account can access the requested resource in the service itself. PersonaStack cannot use a project, channel, or repository that account cannot reach.

2. Check the persona assignment

Open the affected persona’s settings. Under Integrations, confirm that the intended saved connection is selected. Names matter when you have several accounts connected to the same service.

If the connection does not appear, check the current workspace. If the controls are disabled, read the message next to them. Some integrations for linked Hermes or OpenClaw personas are managed on the external host.

3. Check access for the action

Sending a message needs sending access where the integration offers that setting.
Reading needs the appropriate access and selected conversation or resource scope.
Starting work from a message also needs receiving configured and Wake on incoming events enabled for that persona.
Selected scope with no selected resources is not permission to use everything.

For Slack, check both reading scope and wake mode. For Discord, check server selection and DM settings. For Telegram, check group-response rules. For Matrix, check the device status and watched rooms.

An event arrived but no persona responded

Check the integration’s status first, then the persona’s pause state, provider, and quotas. Send one simple message from a different account in an allowed conversation.

For Incoming Webhook, open View webhook history. An accepted event can appear there before a persona is attached. Confirm that the webhook panel shows attached recipients, then inspect the persona’s Run Logs.

A skill appears but its tool is missing

A skill supplies instructions. It does not supply every service account or permission those instructions mention. Read the skill’s requirements and connect the needed integration.

Check the skill’s selected state and any preparation or budget message in Skills. For a custom skill, check its selection in Skills or under Knowledge. For an external persona, confirm that its host supports the MCP Skills extension. Refresh the host’s skill list and check its approval and dependency requirements. A saved PersonaStack selection does not prove the host loaded it.

A desktop command cannot run

Check the persona's Desktop Control selection and the computer's access and readiness status. Keep the computer awake and the PersonaStack app running. Resume control if it is paused. If the app reports an unsupported command operation, update the desktop app.

Check that the command's directory exists on that computer and that its signed-in account can use the required files and programs. For a program that needs a terminal, ask the persona to use interactive terminal mode. Read a running command's output before supplying input. A busy result means another persona holds the computer's control lease.

If output reports a gap, some bytes are no longer available in the bounded output buffer. Narrow the output or have the command write a result file on the computer. If a command's outcome is unknown, inspect the current state before deciding whether to run it again. See desktop command access.

Try one specific operation

Ask for one small result, such as reading a named project’s open tasks. Specify the account or connection when there is more than one. Open Run Logs and inspect the failed step instead of repeatedly sending the full original task.

Share useful details

Email support@personastack.ai from your registered address. Include the integration and persona names, the time and timezone, the operation attempted, and the visible error. Include a run link when available.

Keep tokens, Security Phrases, full webhook URLs, and private message contents out of the report.

Need a hand? Contact the PersonaStack team.