Troubleshooting agents

Sign-in problems

The sign-in page didn't open. Start it again from your agent. In Claude Code, run /mcp, pick bidhelm and choose Authenticate. In Codex, run codex mcp login bidhelm.

The page says "Sign-in can't be reached right now." The sign-in service didn't load. Wait a minute and start the connection from your agent again.

The page says "This link is missing its sign-in details." The page was opened without the request your agent sends with it, for example from a bookmark or a copied link. Start the connection from your agent again so it opens the page itself.

You weren't signed in. Bidhelm sends you to sign in first, then brings you back to the page where you select Allow.

Your agent asks you to sign in again. Sign in and select Allow. Once the connection is approved, your agent stays signed in.

Your client can't register

Bidhelm signs in clients that identify themselves with a client ID metadata document, as the current MCP spec describes. A client that only supports dynamic client registration can't connect yet. Claude Code, Codex and Claude all connect. For another client, check its documentation for client ID metadata document support.

Your agent can't find a workspace

Your agent sees the workspaces that your login belongs to, nothing else. Ask it to call list_workspaces to see them.

A workspace whose plan has ended also reads as not set up. Pick a plan again under Settings › Plan & billing. See Cancel or delete your account.

A change is refused

"This needs an owner or admin of the workspace." Your role is Member, and this change needs an owner or admin, just as it does in the dashboard. That covers Permissions, social settings, posts in the queue, inbox replies and moderation, and social rules and built-in defaults in Memory. Ask an owner or admin to make it, or to change your role. See Members and roles.

"…is permanent; call again with confirm: true to go ahead." The change can't be undone, so the tool waits for confirmation. Your agent should ask you before it calls again. See What your agent can do.

"No Google Ads account connected in this workspace." The ads tools need a connected Google Ads account. Connect one under Settings › Connections. See Connect Google Ads.

"Google Ads needs to be reconnected." Bidhelm's access to your Google Ads account stopped working. Reconnect it in the dashboard under Settings › Connections.

Nothing was sent on a budget or bid change. set_budgets and set_keyword_bids hold back a change that's more than five times the current amount, and set_budgets also holds back a budget shared with other campaigns, a raise with no monthly plan to check it against, and one that would take the month more than 10% over your monthly plan. The answer names the reason for each campaign or keyword.

An id isn't found. Every "not found" answer names the tool that returns a valid id, such as list_drafts for a draft or get_campaigns for a campaign. Your agent can call that tool and try again.

Slow or unfinished answers

ask_question and request_action can answer with a running status while Bidhelm works. Your agent reads the result with ask_question and the chat's id. A report started with run_report takes a few minutes, and only one runs at a time in a workspace.

Too many requests, or every call refused

"Too many requests." Your agent sent a burst of calls in a short time. Wait a minute and try again.

Every call is refused with "Forbidden". Your account can't use Bidhelm right now. Contact Bidhelm from the email address on the account.

"Something went wrong on Bidhelm's side." Try again. If it keeps happening, contact Bidhelm with the time it happened.

Common questions