Troubleshooting AI apps

Find what you see, then open it for why it happens and what to do. Your AI app may put YoPrint’s message in its own words: look for the closest match.

On YoPrint’s sign-in page

These show in your browser, after your AI app sends you to YoPrint. Most of them have a Return to the app button: select it, then start again from the app once the cause is fixed.

“AI apps are not available”

You see:

AI apps are not available for your team. Email support@yoprint.com to ask about your team.

Why: YoPrint has switched AI apps off for your team. This is rare: AI apps are on for every team whose plan includes API access.

Fix: Email support@yoprint.com. Your personal API key and anything built on it keep working.

“AI access is turned off”

You see:

Your team has turned AI access off. The team owner, or anyone who can manage settings, can turn it back on in YoPrint, in Profile under AI apps. Then start connecting again from your app.

Why: The team’s AI access is set to Off, so no one can connect a new app.

Fix: The team owner, or a member with Manage Settings, sets it to Read and change or Read only in Profile > AI apps. Then start again from your AI app.

“AI apps are not included right now”

You see:

AI apps need a plan with API access and an active subscription or trial. Your team doesn't have that right now. Ask your team owner to check the plan, then start connecting again from your app.

Why: The team’s plan doesn’t include API access (it needs Pro or higher), or its subscription or trial has ended.

Fix: The team owner checks the plan and subscription in YoPrint. Then start again from your AI app.

“Your account can’t connect AI apps to your team right now.”

You see: the heading This app could not connect, and:

Your account can't connect AI apps to your team right now. Contact your team owner.

Why: Your YoPrint account isn’t one that can connect AI apps on this team, for example because you’re no longer a member of it.

Fix: Ask the team owner to check your membership.

“This connection request has expired or was opened in another browser.”

You see: the heading Start again from your app, and:

This connection request has expired or was opened in another browser. Go back to your app and connect YoPrint again.

Why: More than 10 minutes passed before you approved, or you finished in a different browser from the one your app opened.

Fix: Go back to your AI app and connect again. Finish in the browser it opens.

“YoPrint is not accepting new AI app connections right now.”

You see: the heading AI app connections are off, and:

YoPrint is not accepting new AI app connections right now. Try again later.

Why: YoPrint has switched off new AI app connections for everyone, for now.

Fix: Try again later. If it lasts, email support@yoprint.com.

“This app sent YoPrint a connection request that YoPrint can’t accept”

You see: the heading This app could not connect, and:

This app sent YoPrint a connection request that YoPrint can't accept, so nothing was connected. Go back to the app and start connecting again. If this keeps happening, contact the app's maker.

Under it, a line that starts “Details for the app’s maker:” names the problem in technical words.

Why: The app sent a request YoPrint can’t accept. Nothing was connected. When the details line starts “resource must be https://mcp.yoprint.com/mcp”, the address added in your app isn’t exactly YoPrint’s: a missing /mcp, an extra slash at the end, or http instead of https all cause it. Other details come from the app, not from anything you did.

Fix: For the address, remove YoPrint from your AI app and add it again with exactly https://mcp.yoprint.com/mcp. Otherwise, start again from the app. If it keeps happening, tell the app’s maker what the details line says.

“YoPrint doesn’t recognize this app”

You see: the heading This app could not connect, and:

YoPrint doesn't recognize this app, so nothing was connected. Go back to the app and start connecting again. If this keeps happening, contact the app's maker.

Why: The app’s registration with YoPrint is missing, or no longer matches the app. An app registers with YoPrint by itself when you add YoPrint to it.

Fix: Remove YoPrint from your AI app and add it again, so it registers again. If it keeps happening and you didn’t start this connection yourself, don’t connect it.

After you select Connect

Usually YoPrint sends you straight back to your AI app, connected. If the approval didn’t go through, YoPrint shows why instead.

One of the messages above, after you selected Connect

Why: Between opening the page and selecting Connect, the team you picked stopped being able to connect. For example, its AI access was set to Off, or its plan or subscription changed. YoPrint shows the same message it would show before approval.

Fix: Follow that message’s fix above, then connect again from your app.

“Your sign-in changed. Start again from your app.”

Why: You signed out, changed your password, or used Logout other devices while the approval page was open.

Fix: Connect again from your AI app.

“You already answered this connection request. Go back to your app.”

Why: The approval was already answered, for example in another tab, or by a second click.

Fix: Check Profile > AI apps > Your connected apps on this team. If the app is listed, it’s connected. If not, connect again from your app.

“Choose read and change, or read only.”

Why: The approval reached YoPrint without an access choice.

Fix: Start again from your app, and select Read and change data or Read only before Connect.

Your app says “The user declined.”

Why: You selected Cancel. Nothing was connected.

Fix: To connect after all, start again from your AI app.

In YoPrint’s Profile

There is no AI apps card in Profile

Why: Your team’s plan doesn’t include API access. It needs Pro or higher.

Fix: The team owner can change the plan. If your plan does include API access and the card is still missing, email support@yoprint.com.

“AI apps need a plan with API access and an active subscription or trial.”

You see:

AI apps need a plan with API access and an active subscription or trial. Ask your team owner to check the team's plan.

Why: Your plan includes API access, but the team’s subscription or trial has ended.

Fix: The team owner starts or renews the subscription in YoPrint.

“Only the team owner, or someone allowed to manage settings, can change this.”

Why: Only the team owner, and members whose role has Manage Settings, can change what AI apps may do on the team. Others see the current level.

Fix: Ask the team owner, or someone with Manage Settings, to change it.

An app you connected isn’t in Your connected apps on this team

Why: The list shows only the apps you connected on the team you’re working in now. Each connection works on one team.

Fix: Switch to the team you picked when you approved the app.

An app shows “Paused”, or “Read only” when you approved changes

You see: under the app, one of these:

• “Paused because AI access is off on this team. It works again when AI access is turned back on.”
• “Approved to read and change. It can only read while this team allows reading only.”

Why: The badge shows what the app can do now. The team’s setting narrows what you approved.

Fix: Nothing to fix on the app. The team owner, or someone with Manage Settings, changes What AI apps may do on this team on the same card.

“Couldn’t disconnect app”, “Couldn’t change AI access” or “We couldn’t load your AI apps.”

Why: YoPrint couldn’t save the change, or couldn’t load the card. An app that was already disconnected, for example from another tab, simply leaves the list.

Fix: Select Try Again, or reload the page. If it keeps failing, contact support@yoprint.com.

What your AI app tells you

It asks you to sign in again, or says “This YoPrint connection is invalid, expired or disconnected. Connect again.”

Why: The connection’s sign-in no longer works. One of these happened:

• You selected Disconnect in Profile > AI apps.
• You changed your password or email, or used Logout other devices.
• The app went unused for 30 days.
• You left the team, or were removed from it.
• The team’s plan lost API access, or its subscription ended.

Fix: Sign in to YoPrint and approve the connection again. In Claude Code, type /mcp, choose yoprint, then Authenticate. If YoPrint’s sign-in page then shows a message, see On YoPrint’s sign-in page.

When the team’s plan is the cause, your app may show one of these instead (api_access_not_in_plan):

This team's plan no longer includes API access. Connect again after the team is on the Pro plan or higher.

This team's plan no longer includes API access, so AI apps cannot work in it. Nothing changed. Tell the person. Someone who manages billing can upgrade to the Pro plan or higher in YoPrint, under Billing.

Connecting again doesn’t help until someone who manages billing changes the plan.

If YoPrint is only briefly out of reach, your app says “YoPrint is briefly unavailable. Try again in a few seconds.” instead. That doesn’t end the connection: wait a few seconds and ask again.

“Team name has turned AI access off.” (ai_access_off)

You see: your team’s name, or “Your team”, then:

Your team has turned AI access off. An owner or settings administrator can turn it back on in YoPrint, in Profile under AI apps. This connection works again then, without connecting again.

Why: The team owner, or a member with Manage Settings, set the team’s AI access to Off. The connection is paused, not removed.

Fix: Ask them to choose Read and change or Read only in Profile > AI apps. The app works again at once, without connecting again.

“Team name allows AI apps to read only.”

You see:

Team name allows AI apps to read only. A team owner can allow changes in YoPrint, in Profile under AI apps. Use read meanwhile.

Why: The team’s AI access is Read only. The app can look things up, but can’t change anything.

Fix: For changes, ask the team owner, or a member with Manage Settings, to choose Read and change.

“This connection was approved for reading only.” or “This connection, or its team, allows reading only, so nothing changed.” (read_only_connection)

Why: You chose Read only when you approved the app, or the team allows reading only.

Fix: If the team allows changes, connect the app again and choose Read and change data. Otherwise see the message above.

“This connection is for another YoPrint team, so nothing changed.” (wrong_team)

Why: A connection works on the one team you picked when you approved it. The app tried to work in a different team.

Fix: To work in the other team, connect the app again and pick that team.

It says your role doesn’t allow it (permission_denied)

You see:

The person's role in YoPrint does not allow this, so nothing changed. Tell them what was refused. A team admin can change role permissions in YoPrint.

Why: Your role in YoPrint doesn’t allow this action. The app has exactly your permissions, checked on every request. Nothing changed.

Fix: Do only what your role allows, or ask the team owner, or a member who manages roles, to change your role.

It says a record is not in your view, or names a rule about your role (not_in_your_view)

You see: a message such as one of these:

• “Your role lets you see only the orders and customers you created or are assigned to.”
• “Your role lets you see only the purchase orders you created or are assigned to.”
• “AI apps can add only this record’s own contacts as recipients: its customer’s, or its vendor’s for a purchase order. Add anyone else in YoPrint.”
• “AI apps can grant only permissions your own role has. Someone who has them, or the owner, can do it in YoPrint.”
• “AI apps cannot change a role you hold: it would change your own access. Someone else who manages roles, or the owner, can do it in YoPrint.”

Why: The app named a record your role can’t open, or tried something YoPrint keeps from AI apps to protect your team: a typed-in recipient, a permission you don’t have, or your own role. YoPrint refused and changed nothing.

Fix: Check the order number or customer name. For a record you can’t see, ask a teammate whose role can. For the other rules, do it in the YoPrint web app, or ask someone who can.

It can’t find a record (not_found)

You see:

That record does not exist, or you cannot see it. Check the id: use the record's `id` field from a list or search.

Why: YoPrint found nothing with that id on this team that you can see. Often the app used a number people see, such as an order number, where YoPrint needs the record’s id.

Fix: Ask the app to look the record up by its number first, then try again. If the record was deleted, it may be possible to restore it in YoPrint.

“AI apps cannot use this operation yet, so nothing changed.” (agent_operation_not_available)

Why: This action isn’t open to AI apps. Some actions never are, such as seeing your API key or changing the team’s AI access. Others are held back for now, such as charging cards, webhooks, the custom portal domain and the next order numbers.

Fix: Do it in the YoPrint web app. See What AI apps can and can’t do.

“AI apps cannot use parameter “value” here.” (agent_action_not_available)

You see:

AI apps cannot use parameter "value" here, so nothing changed. They can use: allowed values. For anything else, tell the person to do it in YoPrint.

Why: AI apps can use this operation, but not this option of it.

Fix: Ask the app to use one of the values the message lists, or do it in the YoPrint web app.

It says the feature isn’t part of the team’s plan (feature_not_in_plan)

You see:

This feature is not part of the team's plan, so nothing changed. Tell the person. Someone who manages billing can change the plan in YoPrint, under Billing.

Why: Your team’s plan doesn’t include the feature the app tried to use. AI apps get only what your plan includes, like the web app.

Fix: Someone who manages billing can change the plan in YoPrint.

It says it’s going too fast and has to wait (rate_limited)

You see: one of these, followed by “Wait N seconds, then send the same request again. A change can keep its key.”:

• “This connection made too many requests in the last minute, so this one did not run.”
• “This team’s AI apps made too many requests in the last minute, so this one did not run.”
• “Too many PDFs or pictures were made in the last minute, so this one did not run.”

Why: One connection made more than 600 reads, 120 changes or 30 renders (PDFs and mockup pictures) in a minute. Or the whole team made more than 1,200 requests, or 60 renders, in a minute, across every AI app. Nothing ran.

Fix: The app gets the wait in seconds (retry_after_seconds) and waits by itself when it can. Otherwise, ask again after that many seconds.

It says the change already ran, or the first try was refused (duplicate_request)

You see: one of these:

• “A request with this key already ran (HTTP 200), so it was not run again. Read the record back to see the result.”
• “The first request with this key was refused (HTTP 422) and nothing changed. Fix the request, then send it with a new key.”

Why: The app sent the same change twice. YoPrint runs a change at most once, so the repeat didn’t run. The answer says how the first try ended.

Fix: Ask the app to read the record back and tell you what it shows. If the first try was refused, the app fixes the request and sends it as a new change.

It says YoPrint doesn’t know whether the change happened (outcome_unknown)

You see:

YoPrint does not know whether the first request with this key made the change. Read the record back to see. If the change did not happen, send it again with a new key.

Why: The first try didn’t finish cleanly, for example it timed out. YoPrint won’t run it again under the same key.

Fix: Ask the app to read the record back. If the change isn’t there, the app sends it again as a new change. If it is there, you’re done.

It says another service didn’t answer (provider_connection_failed)

Why: YoPrint couldn’t get an answer from a shipping, payment or accounting provider. The change may have happened there.

Fix: Ask the app to read the record back before it tries again, so it doesn’t buy or send twice.

It says it can’t give you the answer (response_unavailable)

Why: YoPrint checks every answer for secrets, such as sign-in links, before an AI app sees it. It couldn’t check this one, so it held it back. On a change, the message says whether the change ran.

Fix: For a lookup, look it up in YoPrint yourself. For a change, ask the app to read the record back, and don’t send the change again. If the message says the change was refused, make it in YoPrint.

It says YoPrint has blocked emails from your team (message_sending_blocked)

You see:

YoPrint has blocked this team from sending emails because too many were sent in a short time. Nothing was sent. Stop sending messages and tell the person to contact YoPrint support to lift the block.

Why: Your team sent too many emails in a short time, so YoPrint stopped all emails from it.

Fix: Email support@yoprint.com to lift the block. Ask the app to stop sending messages until then.

It stopped after 30 seconds, or says YoPrint is busy

You see: “The code ran longer than 30 seconds and was stopped.”, or a message that starts “YoPrint is busy”, such as “YoPrint is busy: this connection is already running 2 calls. Wait for one to finish, then try again.”

Why: One call can run for 30 seconds. A connection, and a person, can run 2 calls at once, and a team 4.

Fix: Ask for less at a time, such as one week’s orders instead of a year’s. If it said busy, ask again in a few seconds.

The answer was cut short

Why: One answer holds about 6,000 tokens of text (about 25,000 when the app asks for more).

Fix: Ask for totals, a summary, or just the fields you need, instead of every record in full.

It can’t attach a file you gave it in the chat

Why: The app can’t pass on a file you attach in the chat. Only about 45 KB of copied text fits in its program.

Fix: Put the file at a public link that downloads the file itself, and give the app the link. A file from a link can be up to 10 MB. Or add the file in the YoPrint web app.

It can’t fetch a file from a link (link_refused, upload_not_allowed)

You see: a message that starts with one of these, and says nothing was added:

• “The link could not be reached.”
• “The link answered 404, not a file.”
• “The link redirects too many times.”
• “The file at that link is larger than 10 MB.”
• “The link took too long to send the file.”
• “This type of file cannot be uploaded: web pages, scripts and programs are refused.”

Why: YoPrint fetches files only from public http or https links on the standard ports, up to 10 MB and 20 seconds, following up to 3 redirects. A link that needs a sign-in, or opens a web page instead of the file, doesn’t work.

Fix: Give the app a public link that downloads the file itself, without a sign-in. Or add the file in the YoPrint web app.

“YoPrint could not check its request limits, so this request did not run.” (budget_unavailable)

Why: A short problem on YoPrint’s side. Nothing ran.

Fix: Wait a few seconds and ask again.

For developers

These come from how the AI app calls YoPrint, not from anything the person did. Pass them on to whoever builds or supports the app. See Under the hood.

idempotency_key_required (400)

Why: A change was sent without an idempotency key.

Fix: Send every change from execute with idempotencyKey: a new UUID for each change, such as crypto.randomUUID().

idempotency_key_mismatch (422)

Why: A used key came with a different method, path, query or body.

Fix: Read the record back to see what the first change did, then send the new change with a new key.

request_in_progress (409)

Why: A change under this key is still running.

Fix: Wait a couple of seconds, then call yoprint.operationStatus(key). Don’t send a different change under the same key.

read_tool (403): “This operation changes data, so it runs only in the execute tool.”

Why: A change was sent from read.

Fix: Send changes from execute, with an idempotency key.

“Code is limited to 65536 bytes.”

Why: A program is at most 64 KB.

Fix: Send a shorter program. Fetch data inside the program instead of pasting it in, and bring files in through async_upload/from_url.