> ## Documentation Index
> Fetch the complete documentation index at: https://docs.consile.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> The connector does not show up, a call is refused, or an answer fails? Start here.

*[Læs siden på dansk](https://docs.consile.ai/troubleshooting.md)*

Most problems come from one of four steps: the subscription, your user's access to
the connector, the connection in your AI, or the connection to the data source. Go
through them in that order.

When Consile refuses a call, your AI gets a short message in English, which it
usually passes on to you. The items below quote the most important messages so you
can recognize them.

The portal calls each connection to a system an agreement, and so does this page.

> [!TIP]
>
> If you are an administrator, the **Activity** tab under Team shows every call
> with its outcome and reason, for example *company lock* or *awaiting approval*.
> See [Activity log](https://docs.consile.ai/en/portal/activity.md).

## The connector does not work in your AI

> **The connector does not show up in Claude**
>
> 1. Check in the [portal](https://app.consile.ai) that the connector shows as
>    **Connected** on its page. If it says **Not connected**, it has been
>    bought, but the account is not connected yet. If the organization does not
>    have an active subscription to the connector, your AI gets none of its
>    tools.
> 2. Check that you are logged in to the organization that bought the
>    connector. If you are logged in to another organization, for example a new
>    one, your AI cannot reach the company's data. See *Your AI says you are
>    not subscribed, but the company has bought the connector* below.
> 3. Check that the connector is listed under **Customize → Connectors** in
>    Claude, and that it is turned on in the conversation (**+** →
>    **Connectors**). If it is missing, follow
>    [Connect Claude](https://docs.consile.ai/en/connect/connect-claude.md) again. If you use ChatGPT, see
>    [Connect ChatGPT](https://docs.consile.ai/en/connect/connect-chatgpt.md).
> 4. Start a new conversation. Your AI only fetches the list of tools again in a
>    new conversation, for example after a purchase or after a change to your
>    access.

> **Your AI can only see Consile Concierge, not your data**
>
> The address `https://mcp.consile.ai/mcp` is [Consile Concierge](https://docs.consile.ai/en/concierge.md).
> It can show your MCPs, help with the subscription and send a message to
> support, but it has no tools that read your data. Each connector has its own
> address, for example `https://mcp.consile.ai/gsc/mcp`.
>
> Open the connector in the [portal](https://app.consile.ai), copy the address
> from the **Add it to your AI assistant** card, and add it as a new custom
> connector (see [Connect Claude](https://docs.consile.ai/en/connect/connect-claude.md)).

> **The custom connector cannot be added in Claude**
>
> * Copy the address from the **Add it to your AI assistant** card on the
>   connector's page in the portal, and paste it without spaces before or
>   after.
> * The address is the same for everyone, for example
>   `https://mcp.consile.ai/economic/mcp`. Your Consile login decides which
>   organization and which data you get access to. If you have several
>   agreements in the same system, agreement 2 onwards have their own address,
>   for example `https://mcp.consile.ai/economic-2/mcp`. You copy it with the
>   copy icon next to the agreement on the **Connections** card.
> * On Claude Free you can only have one custom connector.
> * If login fails, remove the connector under **Customize → Connectors**, and
>   add it again with **Register automatically** under **OAuth client**. The
>   login settings cannot be changed after the connector has been added.
> * If a colleague is logged in to the portal in your browser, log out of the
>   portal first. Otherwise the connector is linked to your colleague's login.

## Access and subscription

> **Your AI says the data source is not connected**
>
> The message reads, for example, *"gsc is not connected yet. Connect it here:
> …"*. Your organization has the connector, but nobody has connected the account
> with the provider yet, or the connection has been disconnected.
>
> * Open the link in the message. It works for 10 minutes. If it has expired,
>   ask your AI for a new one.
> * Or open the connector in the [portal](https://app.consile.ai), and click
>   **Connect now** at the top of the page or **Connect** next to the agreement
>   on the **Connections** card (see
>   [Connect your account](https://docs.consile.ai/en/connect/connect-your-account.md)).
>
> Anyone on the team can connect an agreement that is not connected yet. The
> connection is shared by the whole organization, so your colleagues do not need
> to connect again afterwards.
>
> If the company has already connected the system, you may be logged in to
> another organization, for example a new one with the free edition. In that
> case, do not connect again, but see *Your AI says you are not subscribed, but
> the company has bought the connector* below.
>
> CVR has no account to connect. If your AI says you are not subscribed to CVR,
> or that your user does not have access, see the items below.

> **The connector shows as Connected, but every call fails**
>
> **Connected** means that Consile has stored access to the account with the
> provider, not that the provider still accepts it. If the access has expired or
> been removed at the provider, the portal can still show **Connected**. Your AI
> usually gets a message in English saying that the access has expired or been
> refused and that it must be connected again, for example *"HubSpot access
> token has expired; reconnect required"*. In some cases it only gets the
> general error "Tool invocation failed."
>
> Only an administrator can connect an agreement again once it is already
> connected. This is how an administrator does it:
>
> * Open the connector in the [portal](https://app.consile.ai). Click the three
>   dots next to the agreement on the **Connections** card, choose
>   **Disconnect**, and confirm with **Disconnect**. Then click **Connect** next
>   to the agreement.
> * If the agreement shows **Access revoked**, you can click **Reconnect**
>   directly instead.
> * Or ask your AI to connect the connector again. You then get a link that
>   works for 10 minutes, and the new access replaces the old one. If you have
>   several agreements, ask in the connector that belongs to the agreement, for
>   example `economic-2`. Shopify can only be connected in the portal.
>
> If the connection is locked to one company, the company must be chosen again
> afterwards. See *Every call is refused after a new connection* below.
>
> > [!WARNING]
> >
> > The connection is shared. If an administrator disconnects it, everyone in
> > the organization loses access until it is connected again. If your AI says
> > that it is your user who does not have access, the problem is your user
> > access and not the connection. See the next item, and leave the connection
> > alone.

> **Your AI says your user does not have access to the connector**
>
> The message reads, for example, *"Your company subscribes to economic through
> Consile, but your user does not hold a seat on it yet."* Your organization has
> the connector, but it has not been assigned to your user. Each user needs access per
> connector, administrators included. Your AI can see the tools, but every call
> is refused.
>
> 1. Ask an administrator to open your page under **Team** in the
>    [portal](https://app.consile.ai/team) and choose **All tools** for the
>    connector on the **MCPs** card. For e-conomic and Uniconta, the
>    administrator chooses **Read only** or **Full access** instead. If you have
>    the [Consile Studio membership](https://docs.consile.ai/en/portal/membership.md), the administrator
>    clicks **Give the licence** on the **Membership licence** card instead.
> 2. Try again after a moment. Access works within a few seconds, and you do not
>    need to add the connector again in your AI.
>
> Do not buy the connector yourself. The first user per connector is included in
> the price, and each extra user costs 50% of the connector's monthly price. See
> [Team](https://docs.consile.ai/en/portal/team.md). In [the free edition](https://docs.consile.ai/en/portal/free-edition.md), only
> one person can hold the licence.

> **Your AI says you are not subscribed, but the company has bought the connector**
>
> The message reads, for example, *"You are not subscribed to economic. Purchase
> it here first: …"*. The organization you are logged in to does not have an
> active subscription to the connector. There are three typical causes:
>
> * You are logged in to an organization other than the company's, for example a
>   new organization that was created when you logged in without an invitation.
> * A payment has failed, and the subscription is paused. See *The connector
>   stopped working after a failed payment* below.
> * The organization has [the free edition](https://docs.consile.ai/en/portal/free-edition.md), and the
>   system is not included in it. That applies to CVR, for example.
>
> A new organization gets the free edition automatically. If you are logged in to
> one of those instead of the company's, your AI therefore often says that the
> system is not connected rather than that you are not subscribed.
>
> If you are logged in to the wrong organization, do this:
>
> 1. Ask an administrator to invite your email under **Team** and give you access
>    to the connector.
> 2. Log out of the portal, and log in through the link in the invitation.
> 3. Remove the connector in your AI, and add it again. When you log in, it is
>    linked to the company's organization.
>
> Do not buy the connector a second time.

> **e-conomic or Uniconta: your AI can read, but not create or change anything**
>
> The message reads, for example, *"This tool is not enabled for your user on
> economic … Nothing was changed."* (or *uniconta* instead of *economic*).
> Usually an administrator has given your user the access level **Read only**
> for the connector. Your AI only sees the tools that read data, and Consile
> blocks all write operations on the server for your user. Nothing is changed in
> e-conomic or Uniconta.
>
> If you need to create or change data, ask an administrator to choose **Full
> access** for you on your page under **Team**. Both levels cost the same. Then
> start a new conversation so the tool list is fetched again.
>
> If you have just been set to **Read only**, an open conversation can still show
> the write tools. The calls are refused anyway, and a new conversation updates
> the list.

> **A tool is missing, or your AI says it is not enabled**
>
> The message reads, for example, *"This tool is not enabled for your user on
> uniconta … Nothing was changed."* Nothing has been changed. There are four
> possible causes:
>
> * The tool is new and waiting for activation. New tools are turned off for
>   organizations that bought the connector before the tool was released. That
>   applies, for example, to the six daily journal tools in Uniconta for
>   organizations that bought before October 7, 2026.
> * An administrator has turned the tool off for the whole organization.
> * Your user is on **Read only** or **Custom**, and the tool is not included.
> * The connection is locked to one company, and the tool cannot be limited to
>   it. In that case the message reads *"This connection is locked to …, and …
>   cannot be limited to one company, so it is not available here."* instead.
>   See the next item.
>
> An administrator sees and changes the first three on the connector's page in
> the portal and on your page under **Team**. It costs nothing extra. Then start
> a new conversation. See [Tools and new tools](https://docs.consile.ai/en/portal/tools.md).

> **Your AI says the connection is locked to another company**
>
> In Google Search Console, Meta Ads, LinkedIn Ads, Dinero and Business Central,
> an administrator can lock an agreement to one company, for example one website
> or one ad account. Every call on the agreement then keeps to that company.
>
> * If your AI asks for another company, the call is refused, and nothing is
>   fetched or changed. The message begins, for example, with *"This connection
>   only serves \<name>, …"* and tells your AI which company the agreement
>   is locked to. Ask your AI to use that one, or use the connector that belongs
>   to another agreement, for example `dinero-2`.
> * Some tools cannot be limited to one company. Your AI does not see them on a
>   locked agreement, and if it calls them anyway, the message reads *"This
>   connection is locked to \<name>, and \<tool> cannot be limited
>   to one company, so it is not available here."* On Meta Ads that applies, for
>   example, to `update_status` and `update_budget`. This is expected, and the
>   tool cannot be turned on under Team while the agreement is locked.
> * If you ask your AI to show your websites, ad accounts, organizations or
>   companies, it only gets the locked one.
>
> If the agreement is to be used for another company, an administrator clicks
> **Change company** next to the agreement on the **Connections** card. If every
> company should be reachable again, the administrator chooses **Unlock the
> company** in the menu next to the agreement. See
> [Company lock](https://docs.consile.ai/en/portal/company-lock.md).

> **Every call is refused after a new connection: Choose the company again**
>
> If a locked agreement is connected again, for example with a link from your AI,
> the company must be chosen again. Until then, every call on the agreement is
> refused. Your AI gets the message:
>
> > *"This connection is locked to \<name>, but its credential has been replaced since that was confirmed. An administrator must choose the company again in the Consile portal before it can be used."*
>
> On the **Connections** card, the agreement shows *Choose the company again*.
> This is how an administrator does it:
>
> 1. Click **Choose company** next to the agreement.
> 2. The previous company is already selected. Click **Lock to this company**.
>
> If the message instead says that the provider no longer lists the company
> (*"… but the provider no longer lists …"*), the connected account has lost
> access to the company. Connect the agreement with an account that has access,
> or choose another company.
>
> If an administrator disconnects the agreement and connects it again, the lock
> disappears. Your AI can then reach every company the connected account has
> access to, until an administrator has locked the agreement again. See
> [After a new connection](https://docs.consile.ai/en/portal/company-lock.md#after-a-new-connection).

> **The free edition: the 100 calls are used up**
>
> [The free edition](https://docs.consile.ai/en/portal/free-edition.md) gives 100 tool calls a month for
> the whole organization. When they are used up, the call is refused, and nothing
> is changed. The message to your AI begins like this:
>
> > *"This Consile account has used 100 of 100 tool calls included in its plan for \<YYYY-MM>, so the call was not made and nothing was changed."*
>
> * The limit resets at the start of the next month.
> * Calls to a system you have bought as a single connector from the catalogue
>   do not count, and they are never stopped by the limit.
> * An administrator can take the
>   [Consile Studio membership](https://docs.consile.ai/en/portal/membership.md) in the portal. The
>   membership does not have the limit of 100 calls.
>
> In the activity log, such a call is listed with the reason *usage limit
> reached*.

> **A call is waiting for approval or has been rejected**
>
> An administrator can decide that a tool requires approval. The call is then not
> run until an administrator has approved it under **Team** → **Approvals**. See
> [Approvals](https://docs.consile.ai/en/portal/approvals.md).
>
> * **The call is waiting:** The message begins with *"This tool requires
>   approval from an administrator of your organisation's Consile account before
>   it runs."* Nothing has been run. Tell an administrator. Administrators see
>   the number of waiting calls on the **Approvals** tab. Once the call has been
>   approved, ask your AI to run exactly the same call again.
> * **The call is still waiting:** If your AI tries again before anyone has
>   answered, it is told that the request is still waiting (*"Approval request …
>   is still waiting for an administrator's decision."*).
> * **The call has been rejected:** The message begins with *"An administrator
>   rejected approval request …"*. The call is not run. If the administrator
>   wrote a message, it is at the end. Change the request, or talk to the
>   administrator, before you try again.
> * **Too many waiting calls:** The message begins with *"This user already has
>   the maximum number of approval requests waiting for a decision."* One person
>   can have at most 20 calls waiting. Ask an administrator to answer them first.
>
> A call that nobody has answered expires after 48 hours. If the agreement is
> connected again, or the company lock is changed, the call must be approved
> again.

> **The connector stopped working after a failed payment**
>
> If a payment fails, the subscription is paused while the payment is retried.
> Meanwhile, Consile closes the connector's tools. Your AI is told that the
> organization is not subscribed to the connector. Do not buy it again, because
> that creates an extra subscription.
>
> The stored connection to the data source is kept. An administrator updates the
> payment card with **Manage payment in Stripe** under
> [Subscription](https://docs.consile.ai/en/portal/subscription.md). Once the payment has gone through, the
> connector works again by itself, and you do not need to connect the data source
> again.
>
> If the subscription instead ends up being cancelled because the payment does
> not succeed, the stored connection is deleted. The connector must then be
> bought again and connected anew.

> **The buttons for buying, cancelling or payment are gray**
>
> You are a **Member** of the organization. Only an administrator can buy
> connectors, add or remove agreements, open the Stripe portal, cancel
> subscriptions, disconnect a connection, connect an agreement again and delete
> the account. The portal shows *"Only administrators can change the
> subscription - contact your administrator."* The **Connections** card says
> *"Only a team administrator can disconnect or remove an agreement."*
>
> Under **Team** you can see who is an administrator. As a member, you can still
> connect an agreement that is not connected yet.

> **The portal says "This portal changed since the page loaded"**
>
> You clicked **Add agreement** or confirmed **Remove agreement**, but the list of
> agreements has changed since the page was loaded. This happens, for example, if
> you click twice, or if another administrator has just changed the agreements.
> The portal says *"This portal changed since the page loaded. Reload and try
> again."*
>
> Nothing has been bought or removed. Reload the page, check the list on the
> **Connections** card, and try again if it is still needed.

> **An invitation does not arrive**
>
> Ask your colleague to check their spam folder. Then send the invitation again
> from **Team** with the same email. That sends a new email, and the access you
> have already given your colleague is kept. The link in the first email then
> stops working.
>
> If you see *"The invitation couldn't be sent right now"*, try again shortly,
> and write to support if it keeps happening.

> **The link to connect an account shows an error code**
>
> When you open a connection link from your AI, Consile checks again that
> everything is in order. If you see a short error code in the browser, it means:
>
> * `invalid_or_expired_link`: the link is more than 10 minutes old. Ask your AI
>   for a new one.
> * `tos_not_accepted`: you have not accepted Consile's terms yet. This applies
>   per user, so new colleagues usually meet it the first time. Open the
>   connector in the [portal](https://app.consile.ai), and start the connection
>   from there. You are then asked to accept the terms first.
> * `not_entitled`: the organization does not (or no longer) have an active
>   subscription to the connector, or the subscription is paused after a failed
>   payment.
> * `admin_required`: the agreement is already connected, and only an
>   administrator can connect it again.
> * `connect_requires_portal_input`: the connector needs details that can only be
>   entered in the portal. That applies to Shopify, where the store domain must
>   be filled in. Connect it in the portal.
> * `account_pending_deletion`: the account is being deleted. If you want to undo
>   that within the 14 days, write to support.

## Studio

> **An own connector gives no tools**
>
> Your AI gets no tools from an [own connector](https://docs.consile.ai/en/studio/own-connectors.md) in
> Studio. The message to your AI says why:
>
> * *"This Consile Studio connector is deactivated."* The connector is
>   deactivated. In Studio it has the label **Deactivated** and is on the
>   **Deactivated** tab. The owner or an administrator clicks **Activate**. A
>   member can also activate one that is shared with them, or one that shows
>   *The owner has left the team*. Whoever activates it becomes the owner. See
>   [Deactivation and activation](https://docs.consile.ai/en/studio/own-connectors.md#deactivation-and-activation).
> * *"This Consile Studio connector is not available to the signed-in Consile
>   account …"* Only the owner and the colleagues the connector is shared with get
>   tools from it. That applies to administrators too. Ask an administrator to
>   share it with you.
>
> If only some tools are missing, check your access under **Team**. Each person
> only gets the tools in the connector that they have access to themselves. An
> agreement that is paused in Studio gives no tools either. See the next item.

> **An agreement shows as Paused in Studio**
>
> An agreement that belongs to a customer in Studio is paused when it has been
> connected again and Consile cannot confirm that it still belongs to the same
> customer. Meanwhile, the customer's own connectors cannot use the agreement's
> tools. Your AI does not see them.
>
> * If it says *Paused: the connection was renewed and we could not confirm it is
>   still \<customer>. Pick \<customer> again to confirm it.*, an
>   administrator chooses the customer again for the agreement.
> * If it says *Paused: the company is not confirmed.*, the agreement is in one of
>   the five systems with company lock. An administrator clicks **Choose the
>   company again** and chooses the same company. Choosing the customer again does
>   not help here.
>
> See [Customers](https://docs.consile.ai/en/studio/customers.md).

> **An AI bot is refused**
>
> An administrator sees the bot's status in Studio and on the bot's page.
>
> * **Paused:** Calls with the key are refused. Click **Resume**.
> * **Blocked:** The key is blocked. Click **Make a new key**, and put the new key
>   into the bot's platform.
> * **Deactivated:** Click **Activate**. The bot is still paused afterwards, so
>   click **Resume** too.
> * If the bot gets the message *"This bot has reached its limit of … calls per
>   …"*, it has used its limit per minute or per day. The limits can only be
>   lowered.
>
> The **Activity** card on the bot's page shows the reason for each refusal. See
> [AI bots](https://docs.consile.ai/en/studio/ai-bots.md).

## Errors in the answers

> **Your AI gets the error "Tool invocation failed."**
>
> This is Consile's general error message when a call to the data source does not
> succeed and there is no more precise message to give. The provider's own error
> text is not passed on, so your AI cannot see the exact cause. The typical causes
> are:
>
> * The provider did not answer in time or is down. Try again shortly, or ask for
>   a shorter period or fewer rows.
> * The provider limits the number of calls. Wait a minute, and ask again.
> * An argument is invalid, for example a date in the wrong format. Ask your AI to
>   try again with other values.
> * The provider refuses the lookup, for example because the connected user does
>   not have access to that particular data.
>
> If the access has expired or been refused at the provider, your AI usually gets
> a message saying that the connector must be connected again instead (in
> English, for example "… reconnect required"). Connect the connector again (see
> *The connector shows as Connected, but every call fails* above).
>
> Some connectors also send a specific message in other cases. e-conomic, for
> example, says which field was refused, or that e-conomic limits the number of
> calls. Ordrestyring and Business Central say when too many calls have been
> sent, and Business Central also says when the connected user lacks access. The
> same applies when Uniconta refuses a change in the daily journal (see
> *Uniconta: a change in the daily journal was refused* below).
>
> If the error continues, write to support with the time and the question you
> asked.

> **An answer gives empty figures**
>
> * The period may have no data, or the login connected at the provider does not
>   have access to the account, company or property you are asking about. Ask
>   your AI to show the resources it can see first.
> * If the agreement is locked to one company, your AI can only see that company.
>   See [Company lock](https://docs.consile.ai/en/portal/company-lock.md).
> * If you have several agreements in the same system, check that you are asking
>   in the right one. Each agreement is its own connector in your AI.
> * If it keeps happening, write to support with the time and the question you
>   asked.

> **Calls are refused with "Rate limit exceeded"**
>
> Consile limits how many requests your account can send to the same connector
> per second. The limit is usually only reached if an agent or a script sends many
> calls right after each other. Wait a moment, and try again. The current limits
> are listed under [Errors & limits](https://docs.consile.ai/developers/errors-and-limits.md).

## Problems with a specific connector

> **Meta Ads: every call fails, or the access has expired**
>
> Meta Ads usually has to be connected again about every 60 days. The connection
> also stops working if Consile is removed in your Facebook settings. The portal
> can still show **Connected**, and Consile sends no reminder before the
> connection expires. Your AI usually gets the message *"Meta access token has
> expired; reconnect required"* or a similar message saying that Meta has refused
> the access. In some cases it only gets the error "Tool invocation failed." on
> every Meta Ads call.
>
> This is how an administrator connects again:
>
> 1. Open Meta Ads in the [portal](https://app.consile.ai).
> 2. Click the three dots next to the agreement on the **Connections** card,
>    choose **Disconnect**, and confirm with **Disconnect**. Then click
>    **Connect**.
> 3. Log in with your Meta account, and approve the access again.
> 4. If the agreement was locked to one ad account, lock it again. See
>    [Company lock](https://docs.consile.ai/en/portal/company-lock.md).
> 5. Start a new conversation in your AI.
>
> An administrator can also ask your AI to connect Meta Ads again. You then get a
> link straight to Meta's approval. The link works for 10 minutes. For an extra
> agreement, ask in the connector that belongs to the agreement, for example
> `meta-ads-2`. A locked agreement keeps its lock, but the company must be chosen
> again.
>
> > [!NOTE]
> >
> > The connector sees the ad accounts and Pages that the connected Meta user has
> > access to and that you gave access to in Meta's dialog. If an ad account is
> > missing, check the Meta user's access, and connect again. If the agreement is
> > locked, your AI only sees the locked ad account.

> **Meta Ads: your AI only shows a preview, and nothing is created**
>
> This is the intended behavior. The Meta Ads connector protects you against
> unintended spending:
>
> * New campaigns, ad sets and ads are created with the status **PAUSED** by
>   default. Creating them as active requires your confirmation.
> * Activating, archiving and changing a budget also require confirmation
>   (`confirm: true`). Without confirmation, the tool returns a preview and does
>   not call Meta. Pausing something happens immediately.
>
> If your AI shows a preview and nothing more happens, reply something like
> *"Yes, confirm and do it."* Your AI then sends the call with confirmation.
>
> See [Actions & guardrails](https://docs.consile.ai/en/essentials/actions-and-guardrails.md) for an
> overview of which actions require confirmation.
>
> > [!NOTE]
> >
> > The connector cannot delete campaigns, ad sets or ads. It can archive them,
> > so they are inactive but still in your Meta account. On an agreement that is
> > locked to one ad account, your AI can neither activate, pause, archive nor
> > change a budget.

> **LinkedIn Ads: tools for company pages and posts are not available yet**
>
> 22 of LinkedIn Ads' tools are not available yet: 8 tools that create, change
> or delete organic posts, comments and reactions, and 14 tools that read company
> pages, posts and your own profile. The list is in
> [Actions & guardrails](https://docs.consile.ai/en/essentials/actions-and-guardrails.md).
>
> Calls to them fail, usually with "Tool invocation failed.", and nothing is
> posted or changed. The tools for ad accounts, campaigns, reporting, audiences,
> conversions and lead forms work normally.

> **LinkedIn Ads: your AI only shows a preview, and nothing is created**
>
> Same principle as Meta Ads. The LinkedIn Ads connector protects you against
> unintended actions:
>
> * New campaign groups and campaigns are created as **DRAFT** by default. Making
>   them go live right away requires your confirmation. Ads cannot be created
>   through the connector.
> * Activating, archiving and changing a budget or bid require confirmation
>   (`confirm: true`). Without confirmation, the tool returns a preview and does
>   not call LinkedIn.
> * Changing the name, end date and targeting happens without confirmation, also
>   on a campaign that is running. The same applies when something is paused or
>   set to draft status, and when conversion rules are created, changed or
>   attached.
>
> Reply to your AI with something like *"Yes, confirm and do it."* to complete an
> action that is waiting for confirmation. See
> [Actions & guardrails](https://docs.consile.ai/en/essentials/actions-and-guardrails.md) for an overview.

> **Shopify: Authorise access cannot be clicked, or every call fails**
>
> * The **Authorise access** button is gray: the **Store domain** field only
>   accepts the store's Shopify domain, for example `my-store.myshopify.com` or
>   just `my-store`. Write it without `https://`, and do not use the store's own
>   domain (for example `www.my-store.com`). You find the domain in the Shopify
>   admin under **Settings → Domains**.
> * The link from your AI does not work: Shopify can only be connected in the
>   portal, because the store domain has to be entered there. The browser then
>   shows the error code `connect_requires_portal_input`.
> * Every Shopify call fails with a message saying that the access has expired or
>   been refused ("… reconnect required"): an administrator connects the store
>   again. Click the three dots next to the agreement on the Shopify page in the
>   portal, choose **Disconnect**, confirm with **Disconnect**, and then click
>   **Connect**.
> * If you want to connect an extra store, write to
>   [support@consile.dk](mailto:support@consile.dk). It cannot be done in the
>   portal today.

> **Dinero: answers fail for an organization**
>
> Most errors from Dinero only reach your AI as "Tool invocation failed." The
> typical causes are:
>
> * Dinero Pro is missing. Dinero's API only works for organizations on Dinero
>   Pro. Ask your AI to show your Dinero organizations, and it can see which ones
>   have Pro. If the agreement is locked to one organization, it only shows that
>   one.
> * Your Visma login does not have access to the organization you are asking
>   about.
> * Many questions have been asked in a short time. Dinero allows about 100 calls
>   a minute per organization. Wait a minute, and ask again.
>
> If the access has expired or been revoked at Visma, your AI instead gets a
> message saying that Dinero must be connected again ("… reconnect required"). An
> administrator connects Dinero again in the portal.

> **Ordrestyring: amounts look wrong, or a case cannot be found**
>
> * The amounts seem to be 100 times too large: Ordrestyring does not state which
>   unit the amounts are delivered in (their older API used øre, the Danish unit
>   of 1/100 krone), and Consile passes the figures on unchanged. Compare one case
>   you know with the figures in Ordrestyring, and then ask your AI to convert if
>   the figures are in øre.
> * A case cannot be found: the case number is not the same as the case's id.
>   Your AI finds the case with `find_cases`, which only searches the most
>   recently updated cases (600 by default, at most 1,000). If the case has not
>   been changed for a long time, ask your AI to page through the cases with
>   `list_cases`, which can go through the whole list page by page.
> * The other error messages from Ordrestyring are explained under
>   [Connect Ordrestyring](https://docs.consile.ai/en/connect/connect-ordrestyring.md#if-a-lookup-fails).

> **e-conomic: booking the daily journal was refused**
>
> `book_journal_entries` only books entries that are unchanged since the
> preview. If an entry has been changed in the meantime, the whole call is
> refused (the message begins with "Entries changed since the preview"), and
> nothing is booked. Ask your AI to show the preview again, and confirm anew.

> **Uniconta: your AI sees only one company or no company**
>
> `list_companies` only shows the company the agreement is set up with (its
> Company ID), even if the server user has access to more. Each company needs its
> own agreement, and each agreement is its own connector in your AI, for example
> `uniconta-2`.
>
> Ask your AI: *"Which Uniconta company are you connected to?"*
>
> * If you get the company's name, the login and Company ID are in order.
> * If your AI finds no company, the login works, but the Company ID does not
>   match a company the server user has access to. Find the correct **CompanyId** in
>   Uniconta, and ask an administrator to connect the agreement again with it.
> * If your AI gets a message saying that it must be connected again
>   (`reconnect required`), it is the login that is wrong.
>
> See [Connect Uniconta](https://docs.consile.ai/en/connect/connect-uniconta.md#if-a-lookup-fails).

> **Uniconta: a change in the daily journal was refused**
>
> The message reads, for example, *"Uniconta refused … Nothing was changed."*
> Uniconta has refused the change, and nothing has been changed. The reason is in
> the message. A typical cause is that the server user only has read access. Give
> it write access to the daily journal and the right to post in Uniconta
> (see [Connect Uniconta](https://docs.consile.ai/en/connect/connect-uniconta.md)). If the message instead
> mentions, for example, an unknown account, ask your AI to correct the proposal
> and try again.
>
> `post_journal_lines` only posts lines that are unchanged since the preview. If
> a line has been changed in the meantime, the posting is refused, and nothing is
> posted. Ask your AI to show the preview again, and confirm anew.

## Remove all Consile access

### 1. Disconnect in the portal

An administrator opens the connector's page in the [portal](https://app.consile.ai),
clicks the three dots next to the agreement on the **Connections** card, chooses
**Disconnect** and confirms with **Disconnect**. The stored access at Consile is
then deleted immediately. If the agreement is locked to one company, the lock also
disappears. Disconnecting applies to the whole organization, and the subscription
continues until an administrator cancels it under
[Subscription](https://docs.consile.ai/en/portal/subscription.md).

If you have several agreements, you disconnect each agreement separately. An
administrator removes an extra agreement with **Remove the agreement** in the same
menu and confirms with **Remove agreement**. If you remove an agreement other than
the last one, the last agreement moves up into the free slot and takes its address.
If it is locked, the company must be chosen again. So check the addresses on the
**Connections** card afterwards, and correct them in your AI.

### 2. Remove the access at the provider

Consile does not revoke the access at the provider itself. If you want to be sure
that the access is also gone at the source, do this:

| Connector | How to remove the access at the provider |
| - | - |
| Google Search Console | Remove Consile under [Third-party connections](https://myaccount.google.com/connections) in your Google account |
| Meta Ads | Remove Consile under [Business integrations](https://www.facebook.com/settings?tab=business_tools) in your Facebook settings |
| LinkedIn Ads | Remove Consile under [Permitted services](https://www.linkedin.com/psettings/permitted-services) in your LinkedIn settings |
| e-conomic | Remove the Consile app under the agreement's app settings in e-conomic. If you have connected several agreements, do it on each agreement |
| Dinero | Revoke the Consile app's access under the app and integration settings of your Visma/Dinero account |
| Billy | Delete the access token under **Settings → Access tokens** in Billy. Billy tokens do not expire by themselves |
| Uniconta | Delete the server user you created for Consile, or change its password, under **Company → User rights → Manage users** in Uniconta |
| Ordrestyring | The key does not expire by itself, and you cannot block it yourselves. Contact Ordrestyring's support if it needs to be invalidated or replaced |
| Shopify | Uninstall the Consile app under **Settings → Apps and sales channels** in your Shopify admin |
| HubSpot CMS | Uninstall the **Consile HubSpot CMS** app under **Settings → Integrations → Connected Apps** in HubSpot |
| HubSpot Marketing Email | Uninstall the **Consile HubSpot Marketing Email** app in the same place. It is a separate app, so it must be removed separately |
| Business Central | A Microsoft administrator removes Consile under **Enterprise apps** in the Microsoft Entra admin center |
| CVR | Nothing to remove: CVR uses no account of yours. The access ends when the subscription is cancelled under **Subscription** |

If you want to close the account completely, first cancel the subscriptions under
[Subscription](https://docs.consile.ai/en/portal/subscription.md). Deleting the account does not stop them by
itself. See [Account & data](https://docs.consile.ai/en/portal/account-and-data.md) and
[GDPR & your rights](https://docs.consile.ai/en/essentials/gdpr.md) for deleting your data at Consile.

## Still unsure?

Write to [support@consile.dk](mailto:support@consile.dk). We answer in Danish on the
same working day. It helps if you include:

* which connector it is about,
* what you tried, and when (ideally the question you asked your AI),
* and what happened instead, for example the error message your AI showed.

If you have added [Consile Concierge](https://docs.consile.ai/en/concierge.md) (`https://mcp.consile.ai/mcp`)
in your AI, you can also write directly in the chat, for example *"Contact Consile
support, our Search Console data looks empty today."* Your AI then passes the
message on to us. The **Support** page in the portal collects the contact details.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.