Overview
You asked Moby to make a change, and instead of a success confirmation, you saw an error or the action did not run. This article covers common reasons Moby Actions fail and how to resolve each one.
Find the symptom that matches the message you see in Moby chat.
The error mentions an access token or invalidated session
Issue
The action fails with an error like:
“Error validating access token”
“The session has been invalidated”
“You cannot access the app till you log in to www.facebook.com and follow the instructions given”
Environment
Meta Ads actions.
Cause
The connection between Triple Whale and Meta uses an access token. Meta can expire or invalidate that token after a password change, security reset, or required login prompt.
Resolution
Log in to Facebook directly and complete any security prompts.
Ask Moby to retry the action.
The error mentions permissions or terms that need to be accepted
Issue
The action fails with an error like:
“Ad account owner has NOT grant ads_management or ads_read permission”
“Permissions error”
“Meta Business Tool terms haven’t been accepted”
Environment
Meta Ads actions, including some audience and customer list actions.
Cause
The connected account may be able to read data but not make changes. Some Meta actions also require outstanding Meta terms to be accepted before changes are allowed.
Resolution
In Meta Business Manager, confirm the connecting user has permission to manage ads, not view-only access.
If the error mentions Business Tool terms, open the link in the error message and accept the terms in Meta with a user who can administer the ad account.
Ask Moby to retry the action.
If the error continues after the terms show as accepted in Meta, contact Triple Whale support with the full error message.
The error says the request limit was reached
Issue
The action fails with an error like:
“User request limit reached”
Environment
Any ad platform action, most often during bulk changes.
Cause
The connected platform limits how many changes can be made in a short period. Large batches can hit that limit.
Resolution
Wait before retrying. [
Retry the remaining actions in smaller batches.
The error shows a status code like 400, 500, or 504
Issue
The action fails with a generic error like:
“Request failed with status code 400”
“Request failed with status code 500”
“Request failed with status code 504”
Environment
Any platform action.
Cause
A 400-series code usually means the platform rejected the request. For example, the campaign, ad set, or ad may have been deleted or changed after Moby prepared the action.
A 500-series code usually means the platform had a temporary problem processing the request.
Resolution
Confirm the entity still exists in the connected platform.
Confirm it was not changed or removed after Moby prepared the action.
Ask Moby to retry.
If the same entity fails repeatedly, try making the same change directly in the platform to see whether the platform rejects it there too.
The error mentions an image upload, aspect ratio, or dimensions problem
Issue
A creation action fails with an error that mentions:
“media_upload_error”
“ASPECT_RATIO”
“DIMENSIONS”
“Failed to create asset group”
Environment
Google Ads actions that include images, most commonly Performance Max asset groups or ads.
Cause
One or more images do not meet Google’s requirements for the asset type. Google may reject the whole creation when an image fails its checks.
Resolution
Check Google’s image requirements for the asset type.
Provide replacement images that meet the requirements, or ask Moby to select compliant images from your existing assets.
Ask Moby to retry the creation.
The error mentions a concurrent modification
Issue
The action fails with an error code that mentions:
“CONCURRENT_MODIFICATION”
Environment
Google Ads actions, most often when multiple changes target the same campaign at nearly the same time.
Cause
Google Ads rejected the change because another change to the same object was still being processed.
Resolution
Ask Moby to retry the action.
If you are making several changes to the same campaign, run them one at a time instead of in parallel.
A duplicated ad fails with a Page permission or creative eligibility error
Issue
Duplicating an ad fails with an error like:
“Missing Page permission”
“Ad product ineligible for Advantage+ creative”
A message about a deprecated image crop key
Environment
Meta actions that duplicate an existing ad or reference an existing creative.
Cause
The duplicate reuses the source ad’s Page and creative. Meta re-checks both at creation time. The duplication can fail if the connected user lacks the required Page permission or if the source creative uses a format Meta no longer accepts.
Resolution
For Page permission errors, ask a Page admin to grant the required advertiser access, then ask Moby to retry.
For creative eligibility errors, choose a different source ad.
For bulk duplications, ask Moby to substitute the next best eligible ad when one is blocked.
Still stuck?
Contact Triple Whale support and include:
The exact request you made to Moby
The full error message
The platform
The campaign, ad set, ad, product, or item name
The date and time you ran the action
Related questions
Why did my Moby action fail?
Why did Moby say my account is not allowed to take actions?
What should I do if an action fails because of permissions?
What should I do if Meta says my access token expired?
Why did only some actions in a bulk request succeed?
What should I do if the wrong action ran?
How do I retry a failed Moby action?