The main known bugs on CloudSync and the EventBus module concern data synchronization issues (such as products, orders, or stocks), version incompatibilities, and configuration errors.
- Synchronizations that appear successful (status "green" or code 200), but whose data is only partially available on partner modules (such as Google or Facebook). This can be due, for example, to products wrongly marked as inactive or deleted in the CloudSync database. The recommended solution is then to launch a full synchronization ("Full Sync") of the products to correct inconsistencies.
- Incompatibilities between versions of PrestaShop, modules (EventBus, PS Accounts, etc.), or PHP. It is therefore essential to verify that all modules are up to date and compatible with the version of PrestaShop used. In case of doubt, it is advisable to update the concerned modules.
- Specific errors related to EventBus can also occur, such as the inability to refresh an access token (error 452), incorrect environment configuration (error 453), or database write issues (error 455). For these errors, it is generally necessary to check the server configuration, ensure that access rights are correct, and that the modules are properly installed and up to date.
- Banning certain IP addresses can also block synchronization. PrestaShop support can provide these addresses if in doubt.
- To date, CloudSync is not compatible with the Alma payment module. If you use Alma for payments on your PrestaShop store, it is therefore recommended not to activate CloudSync to avoid any malfunction or data synchronization issues.
For any situation not resolved by these actions, do not hesitate to contact PrestaShop support.