# Troubleshooting 'actions log' errors 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: ### Persistent execution error {% hint style="danger" %} Item failed with the same error 3 times in a row. Aborting. Error was: `{{ }}`. {% endhint %} 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: * [x] Review the error description. * [x] Refer to the any of the sections below for potential solutions. Refer to the 'Error codes' section in the Actions Log module for a list of specific errors: {% content-ref url="/pages/IJYC0oMxLLEDFzaX5jsd" %} [Error messages](/managing-advertising-accounts/modules/actions-log/operation-reports/error-messages.md) {% endcontent-ref %} ### Campaign and ad group location errors {% hint style="danger" %} Failed to locate campaign. Aborting. Failed to locate campaign+ad group. Aborting. {% endhint %} 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: * [x] Verify that the names of campaigns or ad groups are correct—you may need to wait for the changes to be properly indexed. * [x] Ensure no critical cells—campaign name and ad group name— include blank spaces before or after the content in the upload file. ### **Ad group targeting compatibility error** {% hint style="danger" %} Ad group cannot have both keyword and product targets. {% endhint %} This error arises when incompatible targeting types are added simultaneously to an ad group, due to filters/conditions not configured properly. #### Bulk manager If you are submitting operations via the [bulk manager](/managing-advertising-accounts/modules/bulk-manager.md) (search terms add search terms action or ad groups add targeting actions): * [x] Adjust your filters to match the specific targeting type you're trying to add. #### Automated rules If your operations are triggered by [automated rules](#automated-rules): * [x] Adjust your rule conditions to match the specific targeting type you're trying to add. #### Examples * 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. ### Archived entity creation error {% hint style="danger" %} Parent entity is archived forbids child creates. {% endhint %} 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: * [x] Visit the bulk manager ad groups page. * [x] Filter ad groups by status equals "archived". * [x] Lock the filtered records using [lock actions](/managing-advertising-accounts/modules/cross-module-components/data-tables/actions-bar/actions-edit/lock-unlock-records.md). ### Targeting limit exceeded error {% hint style="danger" %} Number of targeting clauses per ad group exceeds the limit. {% endhint %} 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: * [x] Visit the bulk manager ad groups page. * [x] Filter ad groups by targeting count/negative targeting count greater than "990"—or a threshold you consider fitting. * [x] Lock the filtered records using [lock actions](/managing-advertising-accounts/modules/cross-module-components/data-tables/actions-bar/actions-edit/lock-unlock-records.md). ### Archived entity modification error {% hint style="danger" %} Archived entity cannot be modified. {% endhint %} This error appears when trying to modify archived entities. To prevent future *update* operations in archived entities: * [x] Visit the campaigns, ad groups and/or targeting pages. * [x] Filter records by status equals "archived". * [x] Lock the filtered records using [lock actions](/managing-advertising-accounts/modules/cross-module-components/data-tables/actions-bar/actions-edit/lock-unlock-records.md). ### Bid value errors {% hint style="danger" %} 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. {% endhint %} 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: * [x] [Set bid boundaries](/managing-advertising-accounts/modules/bulk-manager/targeting/update-targeting/update-targeting-bid/targeting-bidding-parameters.md#bidding-boundaries) within Amazon's limits. * [x] Ensure campaign budgets are sufficient to accommodate bid values. ### **Auto-targeting modification error** {% hint style="danger" %} Auto-targeting targeting clauses cannot be changed manually. {% endhint %} 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: * [x] Visit bulk manager targeting page. * [x] Filter targeting by contains "targeting\_auto". * [x] Lock the filtered records using [lock actions](/managing-advertising-accounts/modules/cross-module-components/data-tables/actions-bar/actions-edit/lock-unlock-records.md). ### **Ended campaign modification error** {% hint style="danger" %} Ended campaign cannot be updated without end date extension. {% endhint %} This issue arises when modifying campaigns with past end dates. If you are looking to allow the ended campaign(s) to serve: * [x] Log into amazon console. * [x] Either extend the campaign's end date or remove it entirely. * [x] Submit your change again via the app, after making sure the change executed in amazon has been indexed. If you do not wish to modify ended campaigns further: * [x] Visit bulk manager campaigns page. * [x] Filter campaigns by end date is not blank AND end date is less than `{{ TODAY }}`—write today's date in `YYYY-MM-DD` format. * [x] Lock the filtered records using [lock actions](/managing-advertising-accounts/modules/cross-module-components/data-tables/actions-bar/actions-edit/lock-unlock-records.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.advertisingbeast.com/troubleshooting-the-app/troubleshooting-actions-log-errors.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.