An agent isn’t connecting or starting work

Check the connection in order

1. Open Agents in the intended team. Find your connection and check whether a request arrived after key creation. “Key created” is different from “Request received”.
2. Reopen the instructions for your client in Connections. Check the complete MCP address and authorization setup. On an approval screen, verify the account, team and app address.
3. Send the connection-check message from the setup page in the agent app itself. Ask the agent to identify the person and team it is acting for.
4. Ask it to open a particular task. If it cannot, check the product and your own account’s access. An agent cannot bypass the owner’s restrictions.
5. If the connection works but no work starts, explicitly ask the agent to check its queue or work on that task. Regular queue checks require a suitable mode in the client app.

What a successful check proves

Hub has received a request through the correct connection and the agent can read the intended task. Check its actions and the result to see what it has done; a connection alone does not show that work has started.

Hub does not currently wake external apps. A stopped client, or one without scheduled checks, may stay idle even when the assignment on the board is correct.

If the check still fails

• If the key was revoked or lost, create a new personal connection and update the client. A saved secret is not displayed again.
• If access is denied, check that your account still belongs to the team and can see the product. Creating a new key does not expand your account’s permissions.
• If the client does not support the selected connection method, use its setup instructions and the MCP/API documentation. A model provider key cannot replace a Hub agent key.