Errors from your AI's tools
Messages from Gmail, Outlook, Zendesk, Google Ads, Analytics, stores and calendars that your AI passes on, what they mean and what to do.
When your AI uses a tool and the service refuses or something's wrong with the request, Plugsight explains it in plain words and your AI usually passes it on. In Activity, these show as Failed, with the message underneath. Most are about the request itself, so your AI can often correct it and try again without you changing anything.
Messages any service can give
"…" is the service's name, such as Zendesk, WooCommerce, Magento, Mailchimp, Google or Microsoft. The service's own words often follow in brackets, starting "(… said: …)".
… didn't accept that request. Check the values it names below and try again with corrected ones.
What it means: the service rejected a value in the request, such as a date, field or id.
How to fix it: nothing to change in Plugsight. Your AI reads the service's words in brackets and retries with corrected values. If it keeps failing, rephrase your request.
… no longer accepts this connection's sign-in. Reconnect it on the Connections page in Plugsight.
What it means: the login stopped working.
How to fix it: click Reconnect on the account on Connections. See Reconnect needed.
… says this login isn't allowed to do that. Use an account with access, or ask its admin to grant it.
What it means: the account you connected doesn't have permission for this at the service.
How to fix it: ask the service's admin to give the login access, or connect a login that has it.
… couldn't find that item. It may have been deleted, or the id is wrong: search or list again for a current id.
What it means: the email, ticket, order or other item doesn't exist any more, or your AI used an old id.
How to fix it: ask your AI to search again.
… reported a conflict, usually because the item changed meanwhile. Fetch it again, then retry.
What it means: someone changed the item while your AI was working on it.
How to fix it: ask your AI to read it again and retry.
… is limiting requests right now. Wait a minute, then try again.
What it means: the service's own rate limit was reached.
How to fix it: wait a minute, then ask again. Large questions over long date ranges use more requests.
… is having problems right now. Try again in a few minutes.
What it means: the service is down or overloaded.
How to fix it: try again in a few minutes.
… returned an unexpected error (HTTP …). Try again; if it keeps happening, reconnect the account.
What it means: the service gave an error Plugsight doesn't recognise.
How to fix it: try again. If it keeps happening, reconnect the account on Connections.
This account has no "…" folder. Call list_folders to see what exists.
What it means: your AI asked for a folder name that isn't in this mailbox.
How to fix it: nothing to change. Your AI lists the folders and uses the right name.
This mailbox has no Archive folder. Move it to a folder from list_folders instead (move_to: "<folder>").
What it means: the mailbox has no folder called Archive.
How to fix it: tell your AI which folder to move the emails to.
Labels are a Gmail feature. For this mailbox, move the email to a folder instead (move_to).
What it means: your AI tried to add a label in a mailbox that uses folders.
How to fix it: ask your AI to move the email to a folder instead.
Pick one folder to move to, e.g. "archive", "inbox" or a folder from list_folders.
What it means: your AI asked to move emails to "all", which isn't a single folder.
How to fix it: tell your AI the folder to use.
Nothing to change: pass read, flagged, add_labels, remove_labels or move_to.
What it means: your AI asked to organise emails without saying what to do.
How to fix it: tell your AI what you want: mark read, flag, label or move.
Message not found (it may have been moved or deleted)
Also: Invalid message id "…": use an id returned by search_emails or get_thread for this account.
What it means: the email was moved or deleted since your AI found it, or the id is from another account.
How to fix it: ask your AI to search again.
Draft not found (it may have been sent or deleted).
Also: That email isn't a draft. and The draft has no recipients.
What it means: your AI tried to send a draft that no longer exists, an email that isn't a draft, or a draft with no one to send to.
How to fix it: check the draft in your mailbox, or ask your AI to write a new one.
Add at least one recipient.
What it means: your AI tried to send or draft an email with nobody in To, Cc or Bcc.
How to fix it: tell your AI who it's for.
Attachments total … MB; the limit is 20 MB.
What it means: the attachments are too big to send in one email.
How to fix it: send fewer or smaller files, or share a link instead.
… is larger than 3 MB, which isn't supported for Outlook yet.
What it means: Outlook accounts can't attach files over 3 MB through Plugsight yet.
How to fix it: share a link to the file instead.
Use either reply_to_email_id or forward_email_id, not both.
What it means: your AI tried to reply and forward in one email.
How to fix it: ask for a reply or a forward.
No attachment at index …; this email has ….
Also: … is a link to a cloud file (OneDrive/SharePoint), not a stored file., … is not an email or winmail.dat, so it has no attachments inside. and No file at index …; it contains ….
What it means: the attachment your AI asked for doesn't exist, or it's a link rather than a file.
How to fix it: for cloud links, open the file from OneDrive or SharePoint yourself. Otherwise ask your AI to read the email again.
Could not extract text from …: …
What it means: the attachment couldn't be read as text, for example a damaged or protected file.
How to fix it: open the file yourself.
Zendesk
Zendesk has no ticket or user with that id. Use zendesk_search_tickets or zendesk_find_users to find the right one.
What it means: the ticket or user id doesn't exist, or was deleted.
How to fix it: ask your AI to search for the ticket by subject or requester.
Nothing to change: pass at least one of status, priority, type, assignee_id, add_tags or remove_tags.
What it means: your AI asked to update a ticket without any change.
How to fix it: tell your AI what to change.
Marketing and analytics
Unknown field "…" for …. Call list_marketing_fields.
What it means: your AI asked for a metric or dimension the service doesn't have. The message may suggest similar names.
How to fix it: nothing to change. Your AI looks up the right field and retries.
Unrecognised date "…". Use YYYY-MM-DD, today, yesterday or NdaysAgo.
What it means: your AI used a date format the tool doesn't accept.
How to fix it: nothing to change. Your AI retries with a correct date. You can also give exact dates in your question.
These fields come from different Google Ads reports and can't be combined in one query: …. Split the request.
Also for Microsoft Advertising, and: "…" isn't available together with the other requested fields.
What it means: Google Ads or Microsoft Advertising can't report those fields together.
How to fix it: ask for them in separate questions, or let your AI split the request.
Microsoft Advertising has no field "…".
What it means: your AI asked for a field Microsoft Advertising doesn't offer.
How to fix it: nothing to change. Your AI picks another field.
Report … still pending after 2 minutes; try a shorter date range.
Also: Microsoft Advertising failed to build the report. and Microsoft Advertising did not return a report id.
What it means: Microsoft Advertising took too long to build the report, or failed.
How to fix it: ask for a shorter date range, or try again later.
This report needs connector google_ads or bing_ads.
Also: period_comparison needs a connector. and period_comparison needs fields, e.g. [campaign, cost, conversions, cpa].
What it means: your AI started a ready-made analysis without the details it needs.
How to fix it: nothing to change. Your AI adds the details and retries.
Step "…": give either event or page_contains.
What it means: a Google Analytics funnel step was set up wrongly.
How to fix it: describe each funnel step by an event name or a page address.
Calendar
To move an event, give both start and end.
Also: Nothing to change: pass a new time, title, description, location or add_guests.
What it means: your AI asked to change an event without the full details.
How to fix it: tell your AI the new start and end time, or what to change.
No event with id "…" in "…". Use an id from calendar_list_events.
What it means: the event was deleted or moved, or the id is wrong.
How to fix it: ask your AI to look the event up again.
The event changed in iCloud meanwhile. Fetch it again, then retry.
Also: iCloud didn't accept the event (HTTP …). Try again in a minute.
What it means: the iCloud event changed while your AI was working on it, or iCloud refused the change.
How to fix it: ask your AI to try again.
Contacts and stores
No contact with id "…". Use an id from contacts_search.
What it means: the contact doesn't exist, or the id is wrong.
How to fix it: ask your AI to search for the contact by name or email.
No order "…". Use magento_list_orders to find it.
Also: The store couldn't find that.
What it means: the Magento order number doesn't exist in the store.
How to fix it: check the order number, or ask your AI to list recent orders.
Mailchimp couldn't find that. Check the id (list tools return valid ids).
What it means: the audience, campaign or subscriber doesn't exist.
How to fix it: ask your AI to list audiences or campaigns first.
Mailchimp doesn't allow this key to read that.
What it means: the Mailchimp API key doesn't have access to that data.
How to fix it: create a new key with a Mailchimp account that has access, then reconnect Mailchimp.
The integration isn't allowed to read this. In Magento admin, edit the integration's API resources to include …, save, then reauthorize it.
What it means: the Magento integration can't read orders, products or customers.
How to fix it: see Errors while connecting an account for the exact resources to tick.