Troubleshooting 'actions log' errors
Last updated
Last updated
When submitting operations through the bulk manager, bulk uploads, or automated rules, it's common to encounter errors indicating that not all operations were successful. Some errors may be permanent and unavoidable, but others can be circumvented in future actions. For those errors that can be addressed, alternative solutions and workarounds are available to aid in troubleshooting:
Item failed with the same error 3 times in a row. Aborting. Error was: {{ }}.
This error occurs when the same error triggers three times consecutively, causing the system to abort the operation. Review the specific error code for potential solutions.
To troubleshoot:
Refer to the 'Error codes' section in the Actions Log module for a list of specific errors:
Failed to locate campaign. Aborting.
Failed to locate campaign+ad group. Aborting.
These errors happen when campaigns or ad groups can't be found, often during bulk operations involving children records, for example attempting to add ad groups within a campaigns or targeting within an existing combination of ad group and campaigns without necessarily including the parent entities in the upload.
To troubleshoot:
Ad group cannot have both keyword and product targets.
This error arises when incompatible targeting types are added simultaneously to an ad group, due to filters/conditions not configured properly.
On the search terms page, filter by whether the search term contains or does not contain "B0" (for regular ASINs), or begins or does not begin with "1" (if your ASINs include books, which have a different ASIN structure).
On the ad groups page, filter either by campaign and/or ad group names that you know include the type of record you are attempting to add, or exclude the names that you know are of the other type of record.
Parent entity is archived forbids child creates.
This error occurs when there's an attempt to add targeting to an archived ad group entity.
To prevent future create targeting operations in archived entities:
Number of targeting clauses per ad group exceeds the limit.
This error happens when the limit of targeting added to an ad group is exceeded. It is very common in old campaigns.
To prevent attempts to create targeting in ad groups that have exceeded or are close to exceeding the limit:
Archived entity cannot be modified.
This error appears when trying to modify archived entities.
To prevent future update operations in archived entities:
Keyword was specified with a wrong bid or empty value : {{ }} [minBid: {{ }}, maxBid: {{ }}.
Bid cannot be updated. Outside of allowed range. : {{ }}.
Bid is lower than the minimum allowed by the marketplace.
Bid cannot be negative.
Typically, when performing bidding calculations—often using increase or decrease options—some bids may exceed or fall below Amazon's limits or result in negative values. Although the maximum bid cap on Amazon is usually quite high, exceeding the campaign's budget value can also trigger this error.
To prevent bidding value errors:
Auto-targeting targeting clauses cannot be changed manually.
This reflects failed attempts to manually modify legacy auto-targeting records, which are reported as individual targeting records, even though they do not exist as such within amazon.
To prevent future update operations in legacy auto entities:
Ended campaign cannot be updated without end date extension.
This issue arises when modifying campaigns with past end dates.
If you are looking to allow the ended campaign(s) to serve:
If you do not wish to modify ended campaigns further:
If you are submitting operations via the (search terms add search terms action or ad groups add targeting actions):
If your operations are triggered by :
Lock the filtered records using .
Lock the filtered records using .
Lock the filtered records using .
within Amazon's limits.
Lock the filtered records using .
Lock the filtered records using .