Skip to content
aheldocs

Type to search every page. Use the arrow keys to move and Enter to open.

    Reference and troubleshooting · How-to guide

    Troubleshooting

    Fixes for the common problems with ahel, and how to tell an ahel problem from a vendor problem or a setting in your AI tool.

    Start by finding where the problem is. Most problems sit in one of three places: your AI tool's settings, your ahel workspace, or the app vendor's account. Each section below names the place and the fix.

    Find where the problem is

    You seeIt is usually
    Your AI never mentions ahel, or says it has no such toolThe AI tool: ahel is not added, not signed in, or not switched on for this chat
    ahel answers, but says an app needs setup or is unavailableYour workspace: the app is missing a key, a sign-in, or is off
    The app's own error, such as permission denied or not foundThe vendor: the account or key lacks access, or the record does not exist
    A message that a limit or the monthly request pool was reachedYour plan's limits: see Glossary and limits

    Sign-in finished, but the AI never uses ahel

    1. Open Connect your AI. If your tool is listed as "Connected, signed in", ahel has seen it. If not, the sign-in did not complete: go back to the tool and connect again.
    2. In Claude and ChatGPT, switch ahel on for the chat in the tools menu, then start a new chat.
    3. Mention ahel by name: "Using ahel, list my open issues."
    4. In Claude, choose Always allow when it asks to allow ahel.
    5. If you belong to several workspaces, check that the tool uses the workspace's own address from Connect your AI. Without a workspace in the address, the connector uses the first workspace you joined.

    Some hosts sign in through a browser window. If that window was blocked, allow pop-ups for the AI tool's site and connect again.

    An app says Needs setup

    The app is on, but a key or a sign-in is missing. The detail says which: "Sign in with" the vendor, or "Needs your" vendor "key". Open the app on your Apps page and finish that step. Give an app a key shows where.

    The other status words:

    StatusMeaningWhat to do
    OnReady, nothing missingNothing
    Needs setupOn, but a key or sign-in is missingAdd the key or sign in
    OffThe workspace turned it offSwitch it on, if you may
    AvailableOffered in the workspace, not switched on for youSwitch it on for yourself
    Unavailableahel cannot serve it right now; the detail says whyNothing in your settings fixes this; try later or pick another app

    A card does not appear

    • Cards appear in Claude. In other tools you get the same answer as complete text; that is expected. See What a card is.
    • In Claude, a card that stopped appearing after an ahel release usually means Claude still holds the old list of tools. Open Claude's connector settings and refresh the tools list for ahel, then start a new chat. Asking the AI to list actions does not refresh it.
    • The text answer always carries the full result. If you need to confirm a change and see no card, use the confirm link ahel gives your AI.

    The vendor refuses a call

    The vendor answered, and said no. Check, in the vendor's own settings, that the key or signed-in account has the permission the action needs, and that the record exists. Then replace the key in the vault, or use Sign in again on a sign-in app. ahel cannot grant a permission the vendor account does not have.

    A change did not happen

    • Nobody pressed the confirm card. Changes run only after a person presses it, and a card expires after an hour: "Expired. Nothing ran, and this card will not run." Ask again for a fresh card.
    • On the Team plan, the call may be held for approval. Your AI says "Held for approval" and who has to say yes.
    • Check Activity: each run says whether it completed or needs attention, with what went in and what came out.

    Still stuck

    Get help lists what to send us, and what never to send.

    Last updated 5 October 2026