Logs & Errors
History
Logs
In the History section of your BigCommerce App, you can conveniently review all previous imports you have performed.
The imports are organized in chronological order, with the newest import appearing at the top. Please note that the list is limited to the 30 most recent imports for easy navigation and reference.
Within the History tab, you can find the following essential information related to each import:
1. Starting date and time: This indicates the exact date and time when the import process was initiated.
2. Duration: This refers to the duration it took for the import to complete its execution.
3. Type: The synchronization type can be categorized as either "full" or "delta." A "full" import signifies that all data was imported, while a "delta" import indicates that only the modified or updated data was imported.
4. Scope: The scope denotes the type of job import performed. Currently, there are two available job types:
- Products: This job type focuses on importing product-related data.
- Products with variants: This job type focuses on importing products with variants-related data.
5. Status: For detailed information regarding the synchronization status, please refer to the dedicated Synchronization status section.
6. Message: The Message section provides an overview of the overall health of your job import. To explore further details about the import, simply click on "See logs." This will direct you to a detailed list of job logs categorized by product or other relevant categories.
7. Logs: Within the detailed logs page, you will find errors and warnings associated with the import process. These error messages are designed to be clear and direct, assisting you in identifying and resolving any potential issues that may arise during the import.
By utilizing the comprehensive import history feature in your BigCommerce App, you can easily track and manage your previous imports, ensuring a seamless and efficient workflow for your online store.
Please use this feature to fix all potential errors/warnings in your ito can access the PIM and BigCommerce products concerned by clicking on Go to product.
Please note that you can use the delta import to apply fixes to your import and to preserve the performance of your App.
Synchronization report
The synchronization report is a detailed summary of the synchronization process. It includes information about the sync configuration, tracks the number of resources synchronized, and contains logs for debugging and understanding the synchronization. This report is essential for monitoring and optimizing the synchronization of your resources to BigCommerce.
Log messages
Info
| Log label | Log message |
|---|---|
| Synchronization completed successfully | Synchronization has been successfully completed, with no warnings or errors. |
| Pre-existing product synchronized | PIM Product […]: The PIM product has been synchronized with the BigCommerce product […]. |
| Product creation skipped | PIM Product […]: The PIM product has been skipped because the ‘Import pre-existing products only’ filter was activated. |
| Product created | PIM Product […]: The PIM product has been synchronized with BigCommerce. |
| Pre-existing product model synchronized | PIM Product Model […]: The PIM product model and its variants have been synchronized with the BigCommerce product […]. |
| Product model creation skipped | PIM Product […]: The PIM product and its variants have been skipped because the ‘Import pre-existing products only’ filter was activated. |
| Product model created | PIM Product Model […]: The PIM product model and its variants have been synchronized with BigCommerce. |
Warning
| Log label | Log message |
|---|---|
| Attribute unavailable | PIM attribute […]: The PIM attribute is no longer available in the PIM and has been unmapped from the <…> field. |
| Attribute unavailable in the family | PIM attribute […]: The PIM attribute is no longer available in the […] family and has been unmapped from the <…> field. |
| Incompatible attribute type | PIM attribute […]: The PIM attribute has been unmapped from the BigCommerce field <…> because the attribute type <…> is incompatible. Please map a compatible PIM attribute to the BigCommerce field. |
| Family unavailable | PIM attribute […]: The PIM attribute has been unmapped from the <…> field for the […] family because the PIM family is unavailable. |
| Synchronization completed with warnings and errors | Synchronization has been completed with […] warnings and […] errors. |
| Category does not exist | The BigCommerce category linked to the <…> PIM category doesn’t exist anymore. It has been recreated. |
| No label found | PIM category […]: The PIM category has no label, the category code has been set instead. |
| Product categories not linked | The PIM product categories have not been linked to products because PIM categories have not been synchronized with the app. |
| Product not found | PIM Product […]: The BigCommerce product linked to the PIM product was not found in the BigCommerce store. It has been recreated. |
| Product type not found | PIM product […]: The PIM product has no type, the <…> default value has been set. |
| Product type invalid | PIM product […]: The PIM product type <…> is invalid, the <…> default value has been set. |
| Product model not found | PIM Product Model […]: The BigCommerce product linked to the PIM product model was not found in the BigCommerce store. It has been recreated. |
| More variants in the PIM | PIM Product Model […]: The PIM product model and its variants have been synchronized, but there were more variants on the PIM product model. Missing variants have been created. |
| Asset attribute unavailable | PIM asset attribute […]: The PIM asset attribute is no longer available in the PIM and has been unmapped from media mapping. |
| Incompatible asset attribute type | PIM asset attribute […]: The PIM asset attribute has been unmapped from media mapping because the attribute type <…> is incompatible. Please map a compatible PIM asset attribute. |
| Incompatible asset attribute media type | PIM asset attribute […]: The PIM asset attribute has been unmapped from media mapping because the media type […] is incompatible. Please map a compatible PIM asset attribute. |
| Attribute unavailable for custom fields | PIM attribute […]: The PIM attribute is no longer available in the PIM and has been unmapped from the custom field mapping. |
| Incompatible attribute type for custom fields | PIM attribute […]: The PIM attribute has been unmapped from the custom field mapping because the attribute type <…> is incompatible. Please map a compatible PIM attribute. |
Error
| Log label | Log message | Solution |
|---|---|---|
| Instability error (global_001) | <resource_type> […] cannot be synchronized due to instability. Please try again. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Synchronization stopped manually (synchronization_003) | Synchronization has been manually stopped by a user. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Synchronization stalled | Synchronization has been automatically stopped because it lasted too long. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| PIM API unavailable | Synchronization has been automatically stopped due to the unavailability of the PIM API. Please try again later. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Unknown error | Synchronization has been automatically stopped due to an unknown error. Please try again and contact support if the error persists. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Insufficient app permissions | Synchronization has been stopped due to insufficient app permissions for the current catalog. Please update the category tree and locale permissions in your PIM then try again. | Follow the steps below: 1. In your PIM, go to Connect then Connected apps. 2. Under the Akeneo App for BigCommerce, click on the Manage app button. 3. Go to the Permissions tab and add the missing category trees, locales, and attribute groups. 4. Save, then restart synchronization. |
| Data access error | Synchronization has been stopped due to insufficient app permissions for the current catalog. Please contact support for assistance. | Please contact support via the Helpdesk. |
| Configured channel unavailable | Synchronization has been stopped because the channel <…> is no longer available in the PIM. Please update the store configuration. | Please set an active channel on your PIM. |
| Configured currency unavailable | Synchronization has been stopped because the currency <…> is no longer available for the channel <…>. Please update the store configuration. | Please set an active currency on your PIM channel. |
| Configured locale unavailable | Synchronization has been stopped because the locale <…> is no longer available for the channel <…>. Please update the store configuration. | Please set an active currency on your PIM locale. |
| Identifier unavailable for pre-existing catalog | Synchronization has been stopped because the […] attribute, used as a PIM identifier to match the pre-existing BigCommerce catalog, is no longer available in the PIM. | Please set an active PIM attribute as PIM identifier. |
| Incompatible identifier for pre-existing catalog | Synchronization has been stopped because the […] attribute type, used as a PIM identifier to match the pre-existing BigCommerce catalog, is incompatible. Please map a compatible PIM attribute. | Please set a compatible PIM attribute as a PIM identifier. Compatible attribute types: Identifier, text. |
| No mapped fields | Synchronization has been stopped because none of the native fields are mapped. | Please map at least the required fields to synchronize your products. Required fields: Product name, Default price, Weight, Product type |
| Unmapped required field (td) | Synchronization has been stopped because the following fields are required but not mapped: <…> | Please map the required fields to synchronize your products. Required fields: Product name, Default price, Weight, Product type |
| BigCommerce product error | PIM Product […]: Error on BigCommerce with message: <error_message>. | The solution depends on the error message. |
| BigCommerce product field error | PIM Product […]: Error on BigCommerce field […] with message: <error_message>. | The solution depends on the error message. |
| Instability on product | PIM Product […] cannot be synchronized due to instability. Please try again. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Product identifier value empty or null | PIM Product […]: The PIM product has not been synchronized with a BigCommerce product because the value of the […] attribute, used as a PIM product identifier to match the pre-existing BigCommerce catalog, is empty in the PIM or not linked to the […] family. | Please check your PIM for the following items: • The attribute used as a PIM product identifier is linked to the mentioned family. If not, please link the attribute to the family and fill in the attribute value for the product mentioned. • The attribute value is filled in for the mentioned product. If not, please fill in an attribute value for the product. |
| Product identifier value not unique | PIM Product […]: The PIM product has not been synchronized because the value of the […] field, used as a BigCommerce product identifier to match the pre-existing BigCommerce catalog, is not unique. | Please check which products have the same identifier in your BigCommerce store and assign a unique value to each of these products. |
| BigCommerce product model error | PIM Product Model […]: Error on BigCommerce with message: <api_error_message>. | The solution depends on the error message. |
| BigCommerce product model field error | PIM Product Model […]: Error on BigCommerce field […] with message: <error_message>. | The solution depends on the error message. |
| BigCommerce option not found | PIM Product model […]: An option value for this product has been deleted in BigCommerce but not in the PIM. Please remove the variant in the PIM. | |
| No type found | PIM product model [<resource_identifier>]: The PIM product model has no type, the '<default_value>' default value has been set. | |
| Product model type invalid | PIM product model [<resource_identifier>]: The PIM product model type '<attribute_value>’ is invalid, the '<default_value>' default value has been set. | |
| No variant in the PIM | PIM Product Model […]: The PIM product model has not been synchronized because it has no variant. | Please add a variant to the product model. |
| Instability on product model | PIM Product model […] cannot be synchronized due to instability. Please try again. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Variant identifier value empty or null | PIM Product Model […]: The PIM product model and its variants have not been synchronized because the value of the […] attribute, used as a PIM variant identifier to match the pre-existing BigCommerce catalog, is empty or not linked to the […] family. | Please check your PIM for the following items: • The attribute used as a PIM product identifier is linked to the mentioned family and at the variant level. If not, please link the attribute to the family, at the variant level, and fill in the attribute value for all variants of the product model mentioned. • The attribute value is filled in for the variant of the product model mentioned. If not, please fill in an attribute value for the variant. |
| Variant identifier value not unique | PIM Product Model […]: The PIM product model and its variants have not been synchronized because the value of the […] field, used as a BigCommerce variant identifier to match the pre-existing BigCommerce catalog, is not unique. | Please check which variants have the same identifier in your BigCommerce store and assign a unique value to each of these variants. |
| Variant identifier not at the product variant level | PIM Product Model […]: The PIM product model and its variants have not been synchronized because the value of the […] attribute, used as a PIM variant identifier to match the pre-existing BigCommerce catalog, is not linked to the product variant level of the […] family. | Please check your PIM for the following items: • The attribute used as a PIM product identifier is linked to the variant level of the family. If not, please link the attribute at the variant level of the family, and fill in the attribute value for all variants of the product model mentioned. |
| Different number of variant axes | PIM Product Model […]: The PIM product model and its variants have not been synchronized because it does not have the same number of variant axes as the BigCommerce product […]. | In the PIM or in BigCommerce, restructure your product model so that there are the same number of variant axes. |
| More variants in BigCommerce | PIM Product Model […]: The PIM product model and its variants have not been synchronized because there are more variants on the BigCommerce product […]. | There are two possible solutions: • Create the missing variant in the PIM • Delete the excess variant in BigCommerce |
| Same number of variants but different variant identifier value | PIM Product Model […]: The PIM product model and its variants have not been synchronized because there are variants on the BigCommerce product […] that are not in the PIM. | Please check if it's the same variant on both sides with a different identifier. If so, use a single identifier for this product on both PIM and BigCommerce. |
| Instability on media | PIM <…> […]: Media cannot be synchronized due to instability. Please try again. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Media invalid | PIM <…> […]: The media at […] could not be downloaded and may be invalid. | |
| Media upload error | PIM <…> […]: An error happened during the media […] upload. Please try again. | Restart synchronization. If the problem persists, please contact support via the Helpdesk. |
| Media file size exceeded | PIM <…> […]: The media has been skipped because the file size exceeds the download limit (<…> MB). | |
| Media exceeds server file size limit | PIM <…> [<…>]: The media file is too large and exceeds the server's file size limit. | |
| Media URL too long | PIM <…> [<…>]: The media has been skipped because the link exceeds the BigCommerce URL limit (<…> characters max). | |
| BigCommerce image not found | PIM <…> [<…>]: The image was not found in BigCommerce after its synchronization. Please try again. | |
| Custom field error | PIM <…>: [<…>]: The custom field has not been synchronized in BigCommerce. Message: <…>. | |
| Instability on custom fields | PIM <…> [<…>]: Custom fields cannot be synchronized due to instability. Please try again. | |
| Category already exists | PIM category [<…>]: A PIM category with the same label already exists in <…>. Please change the category’s label in your PIM or in BigCommerce, or change the parent of the existing one in BigCommerce. | |
| Too many subcategories | PIM category [<…>]: The PIM category exceeds the BigCommerce limitation with more than <…> subcategories. The category update has been skipped. Please fix the category tree structure in the PIM. | |
| Label length error | PIM category [<…>]: The PIM category has a label that exceeds the BigCommerce limit of <…> characters. Please shorten the Label in the PIM | |
| Code length error | PIM category [<…>]: The PIM category code exceeds the BigCommerce limit of <…> characters and cannot be set instead of the missing PIM category label. The category creation has been skipped. | |
| Category tree already exists | The PIM category tree cannot be synchronized because there is already a category tree in BigCommerce. | |
| Category not created | PIM category [<…>]: The PIM category was not created because 100 other categories [<…>] with the same label already exist in <…>. Please change the category labels in your PIM. |
Please note that logs returned by the BigCommerce API are not included in the list.