API errors
Every error the Pluto Ads API returns, by its code, with the fields it carries and what to do next.
How an error looks
Errors are application/problem+json (RFC 9457). code is stable, and type links to its section on this page.
title is written for the person or agent reading it. A 422 lists every field problem at once in errors.
{
"type": "https://docs.plutoads.ai/api/errors#invalid",
"title": "The request has 1 problem.",
"status": 422,
"code": "invalid",
"errors": [{ "field": "name", "message": "Use a name of 1 to 120 characters." }],
"requestId": "3f1c9a52-8e0b-4d7a-9c61-0b5e2f7d4a18",
"traceId": "4bf92f3577b34da6a3ce929d0e0e4736"
}Retry a write only with the same Idempotency-Key: the stored result comes back and nothing runs twice. See
Idempotency. Every response carries x-request-id and x-trace-id headers, and every
error repeats them as requestId and traceId. Include them when you report a problem. To follow a request of
yours through, send your own x-request-id (up to 128 letters, digits, -, _, . or :) or a W3C
traceparent.
bad_request
Status 400. The request can't be read: malformed JSON, a wrong type (a JSON number where an amount belongs), a
malformed header such as Pluto-Workspace, or an invalid path or query value. title names the problem. Sending
it again unchanged fails the same way.
unauthenticated
Status 401. There's no credential, or it's invalid, expired or revoked. A revoked key or disconnected agent stops
on its next request. Create a key in SettingsAPI (Settings, then API) with New API key, sign in from your agent again, or
exchange your agent credentials for a new token. See Authentication.
forbidden
Status 403. The credential is valid but can't do this, or it names a workspace it doesn't belong to. title
says which. When a capability is missing, missingCapability names it (for example budgets:write) and
missingCapabilityText says what it allows. A credential never does more than the role of the person it acts for,
narrowed by its own scopes: ask a workspace admin for a credential, or a role, with the access you need. Changes to
what runs at the ad platform need a live capability (ads:publish, budgets:write, delivery:write, ads:delete
or social:write), which the publish scope holds.
{
"type": "https://docs.plutoads.ai/api/errors#forbidden",
"title": "You don't have permission to publish ads.",
"status": 403,
"code": "forbidden",
"missingCapability": "budgets:write",
"missingCapabilityText": "Change live budgets and bids"
}A credential limited to some ad accounts that acts on something in another one, or names another one for something
new, gets 403 with titleCode forbidden_outside_ad_accounts and the title "This credential works only in the ad
accounts it was given.", and no missingCapability. Reading something in another ad account answers
not_found instead. See Ad accounts.
Some steps stay with a signed-in person whatever a credential's access: buying credits, turning on auto top-up or
extra storage, adding to an Enterprise contract, confirming a plan change that charges and opening the billing portal.
title says where the person does it.
An organization can let only its owners and admins create API keys, agent credentials or webhooks. Creating one for
anyone else is 403 with that in title, like "Your organization lets only its owners and admins create API keys.",
and no missingCapability: the role allows it, the organization doesn't. See
the organization's policy.
not_found
Status 404. The item isn't in this workspace. It may have been deleted, or the ID belongs to another workspace:
the API never reveals whether an ID exists elsewhere.
conflict
Status 409. The request is well formed but doesn't fit the current state. The body carries what you need to
resolve it.
Editing and publishing
| Cause | Extra fields | What to do |
|---|---|---|
Someone changed the same field since your expectedVersion | current | Merge with current, then retry with expectedVersion set to current.version |
An Idempotency-Key or commandId reused for a different request | reason: command_id_reused | Use a new key for new work |
| A launch that isn't ready to publish, or an approval that no longer matches it | items | Fix each item, then approve again. An item with action: split_ad_set is an ad set over Meta's 50 ads. |
| Splitting an ad set would put a part below Meta's minimum budget | reason: below_minimum_budget | Raise the budget to the amount title names, or remove some ads |
| Meta's minimum budget couldn't be read for a split | reason: minimum_budget_unavailable | Retry after a moment |
| A split before the launch has an ad account, or with a budget Meta doesn't take | reason: budget_currency_unknown or budget_invalid | Choose the ad account, or fix the budget |
| Pending changes that changed since you reviewed them | revisionsVersion | Read the pending changes again and resend with that version |
| Pending changes Meta can't take | problems or blocked | Fix the listed fields, or discard those changes |
| A live change to a value an imported launch leaves to Meta | managedInMeta | Change it in Meta Ads Manager |
| Meta refused a value in the request | reason: meta_refused, metaField, detail | Change the value Meta names, then retry |
| Meta needs a person to do something in Meta first: confirm it's them, accept terms, pay a balance, or wait out a policy block | reason: meta_needs_person, need, next, link, and who acts: who (one sentence), profile (the Meta profile Pluto publishes with, by name when Meta said it), profileActs (only that profile can do it) | The person who names does it at link in Meta, then retry. GET /integrations/meta/attention lists what's open, and POST /integrations/meta/attention/check confirms it's done; a need that blocks ads (clearsAtPublish) clears only when Meta accepts an ad again, and the check answers atNextPublish instead. Reconnecting Meta doesn't clear it |
| A review status still in use | usageCount | Move its ads to another status first |
| Media a launch that isn't published yet still uses | reason: used_in_unpublished_launch, launches (also on the item's rejected outcome from POST /media/delete) | Remove it from those launches, or archive the media |
| Targeting, audiences or an ad preview without a Meta connection | reason: meta_disconnected | An admin connects Meta |
| The same, after Meta access expired or was revoked | reason: meta_reauthorize | An admin reconnects Meta |
| A comment action the Meta connection lacks permissions for | reason: meta_permissions, missingPermissions | An admin reconnects Meta and grants them |
| Targeting that reaches the EU without the advertiser names Meta requires | reason: eu_advertiser_required, missing, fix | Set the beneficiary and payer (fix links there) |
| An ad preview Meta can't render yet | reason: not_previewable, missing | Add what missing lists |
| A Creative Memory estimate that changed before you accepted it | reason: creative_memory_quote_changed | Get a fresh estimate |
| An archived item, a draft-only action on something live, or a job with nothing to retry | None | Read title |
X launches
| Cause | Extra fields | What to do |
|---|---|---|
| A call that needs X before X is connected | None. title is "Connect X first." | An admin connects X |
| The same, after X access ended | None. title is "Reconnect X first." | An admin reconnects X |
| An X launch that isn't ready to publish, or an approval that no longer matches it | items | Fix each item, then approve again. X has no test run, so these items are every check there is |
| X couldn't be reached, or refused a search for targeting or conversion events | None | Read title, which gives X's reason |
What X refuses while a publish or a live change runs is on the job's item, with the reason in plain words. An app
that reads X's own codes finds the words for each in GET /platforms/x/spec (content.errors):
| Code | Says | What to do |
|---|---|---|
DUPLICATE_TWEET | X already has a Post with this exact text | Change the Post text, then publish again |
TWEET_IS_SPAM | X's checks stopped this Post | Reword the Post, then publish again |
MALWARE_STATUS | X doesn't accept this link | Use another website address, then publish again |
INVALID_PARAMETER | X didn't accept these settings | Check the setting X names, then publish again |
MISSING_PARAMETER | X needs one more setting | Fill in the setting X names, then publish again |
EXCLUSIVE_PARAMETERS | These settings can't be used together | Keep one of the settings X names, then publish again |
Codes starting TOO_MANY | X has a limit here | Remove some of what X names, then publish again |
SPEND_EXCEEDS_BUDGET | The budget is below what's already spent | Raise the budget above what the campaign has spent |
Codes starting FUNDING_INSTRUMENT | X can't charge this funding source | Check the funding source in X Ads Manager, or choose another |
ACTION_NOT_ALLOWED | X doesn't allow this with your role | Ask an account administrator of the ad account to do it, or to change your role |
ACCOUNT_LOCKED_OUT | X has locked this ad account | Open X Ads Manager to see what X asks for |
CURRENT_USER_SUSPENDED | X has suspended the connected X account | Resolve it with X, or connect another X account in Integrations |
READONLY_CLIENT_APPLICATION | Pluto can only read from X right now | Nothing changed on X |
UNAUTHORIZED_CLIENT_APPLICATION | X hasn't approved Pluto for this yet | Nothing changed on X |
Codes ending NOT_FOUND | X no longer has this | Sync X in Integrations |
LOCK_ACQUISITION_TIMEOUT | X was busy with another change | Nothing changed on X |
Pluto's own checks before a publish use the same list:
| Code | Says | What to do |
|---|---|---|
FUNDING_UNABLE | This funding source can't pay for ads | Fix it in X Ads Manager, or choose another funding source |
BID_BELOW_MINIMUM | The bid is below X's minimum | Raise the bid to X's minimum for this currency |
BID_ABOVE_MAXIMUM | The bid is above X's maximum | Lower the bid to X's maximum for this currency |
TWEET_COMPOSER_NEEDED | You can't create Posts as this X account yet | Ask an account administrator to let you create Posts for it, or connect X as that account |
IDENTITY_UNUSABLE | This X account can't run ads for this ad account | Choose another X account, or turn this one on in Integrations |
MEDIA_TOO_LARGE | This file is too large for X | Use an image up to 5 MB, a GIF up to 15 MB or a video up to 8 GB |
MEDIA_TOO_LONG | This video's length doesn't fit X | Use a video from half a second to 20 minutes long |
MEDIA_FAILED | X couldn't process this file | Replace the file and publish again |
Plans and billing
| Cause | Extra fields | What to do |
|---|---|---|
| More workspaces than the new plan holds | reason: too_many_workspaces, limit, used, nextAction: archive_workspaces, upgradeTo | Archive workspaces, or choose the plan in upgradeTo |
| More members or guests than Pro holds, on a checkout for Pro or a switch to it (Pro: 5 members, 10 guests) | reason: too_many_members or too_many_guests, limit, used, nextAction: remove_members or remove_guests, upgradeTo | Remove people or make members guests, or choose the plan in upgradeTo |
| More ad accounts than Pro connects on one platform, on a checkout for Pro or a switch to it (Pro: 3 per platform per organization) | reason: too_many_ad_accounts, limit, used, platform, nextAction: keep_plan, upgradeTo | Stay on the plan in upgradeTo to keep them all |
| More media than Pro includes for the organization's workspaces, on a checkout for Pro or a switch to it | reason: too_much_storage, limit and used in GB, nextAction: delete_media, upgradeTo | Delete media, or choose the plan in upgradeTo |
| A plan change on Enterprise | reason: contact_sales, salesUrl, contactUrl | Talk to sales at salesUrl |
| Cancelling an Enterprise agreement, or deleting its organization, before it ends | reason: agreement_term, runsUntil, salesUrl | Talk to sales at salesUrl |
| A plan change before the organization subscribes | reason: not_subscribed | Start a checkout instead |
| A checkout for an organization that already subscribes | reason: subscribed | Change the plan instead |
| A checkout while another one is being prepared | reason: checkout_in_progress | Retry with the same idempotency key |
| A checkout that ended before it opened | reason: checkout_ended | Start a new checkout with a new key |
| A larger plan and monthly billing in one request | reason: one_change_at_a_time | Upgrade first, then switch billing |
| A second free trial | reason: trial_unavailable | Choose a plan |
| Choosing a plan while the organization is scheduled for deletion | reason: organization_deleting | Restore the organization first |
| Extra storage on Business or Enterprise without a paid subscription | reason: subscription_required, trial, no_subscription or complimentary | Choose a plan first |
| Buying credits or turning on auto top-up on the trial, without a plan or while read-only | reason: choose_plan | Choose a plan first |
| The same on complimentary access without a card on file | reason: complimentary | Contact us. With a card on file, it works as on the granted plan |
| Archiving or deleting the last active workspace | None | To close everything, an owner deletes the organization |
| Restoring an organization after its data started to be deleted | reason: purge_started | It can't be restored |
| Deleting your account while you're an organization's only owner | reason: sole_owner, organizations | Make someone else an owner of each, then retry |
| Transferring ownership to someone who isn't an admin | None | Make them an admin first |
invalid
Status 422. One or more fields break a rule. errors lists every problem, each with a field path (such as
adSets/0/name) and a message. Fix every listed field before you send it again.
Some problems also carry a code and its params, for an app that says the reason in its own words or language:
{
"field": "overrides.cards",
"message": "A carousel holds at most 10 cards.",
"code": "carousel_too_many_cards",
"params": { "max": 10 }
}message is always there, in English, and reads the same with or without a code. A code is stable once it's
sent, and params is an object (maybe empty) whenever code is present. Names and Meta's values in params are
strings, counts and limits are numbers. Treat a code you don't know as if it weren't there and show message. The
same code and params appear beside other reasons the API writes:
- A rejected item of a batch, such as
POST /launches/{id}/ads/batch(errorson the item). - What an import from Meta or Keep in sync left in Meta (
notImporteditems, codes startingnot_imported_). - Why a value of an imported object stays managed in Meta (
managedInMetaentries, codes startingmanaged_). Values from Meta, such as a destination or a performance goal, are inparamsas Meta names them.
Other sentences carry a code under a name of their own, beside the field they code, with the same rules:
- A problem's
title:titleCodeandtitleParams, such asnot_found_the_launchfor "The launch wasn't found." - A batch item's conflict
message:messageCodeandmessageParams. - An import report's kept campaign:
reasonCodeandreasonParamsbeside the campaign'sreason. - A change set's
cannotApproveReason(cannotApproveReasonCode,cannotApproveReasonParams), the reason Pluto wrote for a decision (decision.reasonCode), what it left out (leftOut[].reasonCode), an item's result (result.messageCode) and why a revision made no new version (revisionErrorCode), each with its params.
An X launch's settings answer X's rules, in X's words. field is the path in the request: under
platformSettings.campaign or platformSettings.adSet on a launch, under platformSettings on an ad group, and
settings/utm or overrides.cta for the launch's own content. A value still to fill in (a funding source, a
budget, the X account, a location) isn't a problem here: it's saved, and GET /launches/{id}/publish lists it.
field ends with | message |
|---|---|
bidStrategy | "Maximum bid isn't available for reach campaigns." |
bidAmount | "Autobid takes no bid. Remove it, or choose Maximum bid or Target cost." |
frequencyCap | "X caps frequency for Reach, Engagements and Video views campaigns only." |
placements | "Profiles can't be the only placement on X. Add another." |
adSet.dailyBudget | "Keep the ad group's daily budget within the campaign's." |
campaign.dailyBudget | "The daily budget can't be more than the total budget." |
advertiserDomain | "Enter the domain alone, like example.com." |
settings/utm | "X fills no values in a link. Write each parameter's value out." |
settings/cta, overrides.cta | "Choose a button X offers." |
| Any key | "This setting doesn't exist." or "Choose a value from the list." |
Once a launch is live on X, its ad account, campaign, objective and funding source can't change, and neither can an ad group's placements: "X fixes this once an ad group is live. Duplicate the ad group to change it."
capability_not_grantable
Status 422. A new API key or agent credential, or an agent being connected, asked for access that the person giving
it doesn't have: nobody gives more than they hold. missingCapability names a capability that's missing, as for
forbidden (for example ads:publish), and missingCapabilityText says what it allows. errors lists
every field problem, as for invalid; the one under scopes names the scope you asked for. Ask for less,
or ask someone whose role includes it to create the credential.
When the person's role includes it but their organization lets members' API keys, agent credentials or agents hold
less, it's invalid instead, with no missingCapability: the role allows it, the organization doesn't.
The message under scopes says what the organization allows, and its owners and admins can change that.
{
"type": "https://docs.plutoads.ai/api/errors#capability_not_grantable",
"title": "You can't give access you don't have yourself.",
"status": 422,
"code": "capability_not_grantable",
"errors": [{ "field": "scopes", "message": "You can't grant \"ads:publish\" because you don't have it." }],
"missingCapability": "ads:publish",
"missingCapabilityText": "Publish and launch ads to the platform"
}rate_limited
Status 429. Wait the seconds in the Retry-After header, then retry with the same idempotency key. The causes:
- The credential or its workspace is over its request budget. See Rate limits.
- Meta is throttling, for example on targeting search or ad previews.
- An action with its own hourly limit: invitations, resending an invitation, notifications or contacting sales.
payment_required
Status 402. The organization has no access right now, so it's read-only and nothing changed. feature names what
was refused: writes, publishing, api_access, members or agent. upgradeUrl opens Plan and billing,
where an owner or admin subscribes or updates the payment method.
accessReason says why: no_subscription, trial_ended, canceled, unpaid, past_due (after the grace
period), incomplete, paused, stale (a renewal couldn't be confirmed) or complimentary_ended.
A read-only organization can still:
- Read everything, including exports.
- Pause campaigns, ad sets and ads, and lower budgets. Resuming and raising are refused.
- Turn a loop off, archive it, or delete a draft loop that never ran.
- Approve a change set that only pauses or lowers, reject any change set, and undo a change that pauses or lowers.
- Cancel a publish, a job, a loop run or Creative Memory work.
- Revoke API keys, agents and invitations, delete webhooks, and disconnect Meta.
- Archive or delete workspaces, delete or restore the organization, remove members and leave.
- Use billing, so an owner can always read the state and subscribe.
Everything else answers payment_required. Background syncs from Meta keep running, loops don't run and webhooks
aren't sent. See Billing.
{
"type": "https://docs.plutoads.ai/api/errors#payment_required",
"title": "The free trial ended, so this organization is read-only. An organization owner or admin can choose a plan in Plan and billing.",
"status": 402,
"code": "payment_required",
"feature": "writes",
"accessReason": "trial_ended",
"upgradeUrl": "https://app.plutoads.ai/settings/organization/billing"
}plan_limit
Status 402. The plan doesn't include this, so nothing changed. feature says what, plan is the organization's
plan (pro, business, enterprise, or null during the trial), and nextAction is the next step: upgrade
(to upgradeTo, at upgradeUrl), contact_sales (at salesUrl), keep_plan, add_workspace,
enable_extra_storage or raise_storage_limit.
feature | Meaning | Next step |
|---|---|---|
workspaces | Creating or restoring a workspace past what the plan holds (limit, used). reason: trial (the trial holds 1), plan_cap (Pro holds 3) or scheduled_plan_cap (a move to a smaller plan is scheduled) | upgrade, or keep_plan to cancel the scheduled change |
members | Adding a member past what the plan holds (limit, used, pending member invitations included). reason: plan_cap (Pro holds 5) or trial (the trial too). Complimentary access or an Enterprise contract past its members answers without reason: plan_cap | upgrade to Business; contact_sales for complimentary access and Enterprise |
guests | Inviting a guest past what the plan includes (limit, used, pending guest invitations included). reason: plan_cap (Pro includes 10 per organization) or trial | upgrade to Business, which has no cap |
ad_accounts | Connecting an ad account new to the organization past what the plan holds (limit, used: the distinct ad accounts of that platform connected across its workspaces; each platform counts apart). reason: plan_cap (Pro connects 3 per platform) or trial (the trial too). Accounts already connected stay. A sync adds new accounts up to the cap and holds the rest back: GET /integrations/meta lists them in adAccountLimit.heldBack | upgrade to Business, which has no cap; the first sync after it adds them |
workspace_limits | A monthly credit limit per workspace comes with Business. Removing one works on every plan | upgrade to Business |
usage_breakdown | Usage by workspace and by connected agent come with Business | upgrade to Business |
audit_log | The audit log comes with Business and Enterprise | upgrade to Business |
workspace_access | Giving a member only selected workspaces comes with Business and Enterprise. On other plans members reach every workspace, also when invited from a workspace's own settings | upgrade to Business |
extra_storage | Turning on extra storage on Pro or the trial: Pro's storage is fixed, 50 GB plus 50 GB per extra workspace | upgrade to Business |
media_storage | Media storage is full (limit and used in GB). reason: add_workspace (Pro with fewer than 3 workspaces: each one adds 50 GB), plan_storage (Pro at 3 workspaces), extra_storage_off, storage_limit (the monthly limit an owner or admin set), extra_storage_unavailable or trial | On Pro, add_workspace or upgrade to Business. On Business and Enterprise, an owner or admin turns on extra storage or raises its limit in Limits. On the trial, choose a plan |
creative_memory | Creative Memory needs more credits than are left, more than the contract's Creative Memory allowance left this month (allowance_used), or isn't on the plan (unavailable). reason: credits_used, allowance_used, workspace_limit, member_limit or unavailable | On Enterprise, an owner or admin buys credits or raises the limit, or you wait for next month's credits. Otherwise Creative Memory is an Enterprise add-on: talk to sales |
Nothing waits in a queue: send the request again once the limit changes.
{
"type": "https://docs.plutoads.ai/api/errors#plan_limit",
"title": "Pro holds up to 3 workspaces. Upgrade to Business to add more.",
"status": 402,
"code": "plan_limit",
"feature": "workspaces",
"reason": "plan_cap",
"limit": 3,
"used": 3,
"plan": "pro",
"nextAction": "upgrade",
"upgradeTo": "business",
"upgradeUrl": "https://app.plutoads.ai/settings/organization/billing"
}spend_limit
Status 402. There are no credits for this AI work right now, or a limit was reached, so it didn't start.
Everything that doesn't use AI keeps working. When the organization's credits are used (credits_used), Agent
replies and AI steps in loops don't fail: they wait, with this problem as their reason, and carry on by themselves
once credits arrive.
reason | Meaning |
|---|---|
trial_cap | The free trial's credits are used. An owner or admin chooses a plan. |
credits_used | The organization's credits are used: the included ones and any bought. An owner or admin buys credits, or AI carries on when next month's credits arrive. topUp is pending while an auto top-up is being paid. |
workspace_limit | This workspace reached its monthly limit (targetId, targetName). |
member_limit | This person reached their monthly limit (targetId, targetName). |
loop_limit | The loop reached its own credit limit. Its other steps keep running. |
complimentary_used | This month's credits for complimentary access are used. |
limit and used are decimal strings in currency, where 1 credit is 0.01, and limitCredits and usedCredits
are the same in credits. nextCreditsAt is when next month's credits arrive. resetsAt is when a monthly limit
(member_limit, workspace_limit, loop_limit, complimentary_used) starts again from zero, the 1st of the month
(UTC), and null otherwise. buyCreditsUrl opens Plan and billing, where owners and admins buy credits, and
usageUrl opens Limits, where they change limits. See Billing.
{
"type": "https://docs.plutoads.ai/api/errors#spend_limit",
"title": "This organization's credits are used. Only AI waits; everything else keeps running. An owner or admin can buy credits in Plan and billing, or AI continues when next month's credits arrive on November 1.",
"status": 402,
"code": "spend_limit",
"reason": "credits_used",
"limit": "12.00",
"used": "12.00",
"limitCredits": 1200,
"usedCredits": 1200,
"currency": "usd",
"resetsAt": null,
"nextCreditsAt": "2026-11-01T00:00:00Z",
"topUp": null,
"raisedBy": "organization_admin",
"buyCreditsUrl": "https://app.plutoads.ai/settings/organization/billing",
"upgradeUrl": "https://app.plutoads.ai/settings/organization/billing",
"usageUrl": "https://app.plutoads.ai/settings/organization/spending"
}workspace_archived
Status 409. The workspace is archived: it can be read but not changed. workspaceId and organizationId name
it. An organization owner or admin restores it in the organization's settings. See
Workspaces.
workspace_deleted
Status 410. The workspace is scheduled for deletion, and its credentials were revoked. purgeAfter is when its
data and media are deleted for good. Until then, an organization owner or admin can restore it. After that, its ID
answers 404.
{
"type": "https://docs.plutoads.ai/api/errors#workspace_deleted",
"title": "This workspace is scheduled for deletion on October 26, 2026. An organization owner or admin can restore it until then.",
"status": 410,
"code": "workspace_deleted",
"workspaceId": "0192c9a4-7c1e-7b6e-9a51-3f1d2c4b5a60",
"organizationId": "0192c9a4-7c1e-7b6e-9a51-3f1d2c4b5a61",
"purgeAfter": "2026-10-26T16:41:12Z"
}organization_deleted
Status 410. The organization is scheduled for deletion, with every workspace in it. purgeAfter is the date.
Until then, an organization owner, signed in to the app, can restore it.
member_suspended
Status 403. An organization owner or admin suspended your access to organizationName (organizationId). Your
work stays. Ask them to reactivate you. Your API keys and agents there were revoked and don't come back.
member_removed
Status 403. You were removed from organizationName (organizationId). Your work there stays, and an owner or
admin can invite you again.
unavailable
Status 503. A service the API depends on didn't answer in time. Nothing changed. Retry in a moment with the same
idempotency key. When Meta didn't answer, title says Pluto couldn't reach Meta.
database_unavailable
Status 503, with Retry-After (seconds). Pluto was busy and couldn't answer in time. Nothing changed. Wait
Retry-After seconds and retry with the same idempotency key.
search_busy
Status 503, with Retry-After (seconds), from GET /creative-memory/search and the search_creative_memory
tool. Search couldn't answer just now: the workspace is running as many searches as it may at once, or the database
couldn't answer at all. A search that is only slow doesn't fail: it answers without the part that took too long and
lists it in incomplete. Nothing changed, and it isn't a request budget. Wait Retry-After seconds and search again.
no_result
On a loop run, as an Agent step's error (and the run's): the step ended without writing its report, saying anything
or changing anything, even after it was asked once more for its result, so the steps after it, such as Notify
people, didn't run. Nothing changed. Run the loop
again; if it happens again, make the step's instructions say what result to deliver.
step_limit
On a loop run, as an Agent step's error (and the run's): the step used all of the model calls one step may make in
a run (40; each tool call its code makes counts as one), and the two calls it then got to write its result, reading,
and never wrote its report, said anything or changed anything. So the steps after it, such as Notify people,
didn't run. Nothing changed. The message says how many calls it had, and carries reasonCode loop_step_limit with
reasonParams.limit. Narrow the step's instructions to what the report needs (fewer days, sources or items to read),
then run the loop again.
abandoned
On a loop run, as the run's error: the run stopped before it finished and nothing was left to continue it, so Pluto
ended it and closed the steps it hadn't reached. What its earlier steps did and delivered stays as it was. Start the
loop again.
sign_in_unavailable
Status 503, from POST /auth/magic/verify. Signing in couldn't finish just now. Nothing was wrong with the code,
and it still works: send the same code again.
internal
Status 500. Something failed on our side, and we logged it. title reads "Nothing was changed." Retry with the same
idempotency key, and include the error's requestId when you report it.