The main known bugs in CloudSync and the EventBus module pertain to data synchronization issues (such as products, orders, or inventory), version incompatibilities, and configuration errors.
- Synchronizations that appear to be successful (status "green" or code 200), but for which the data is only partially available on the partner modules' side (such as Google or Facebook). This may be due, for example, to products incorrectly marked as inactive or removed in the CloudSync database. The recommended solution is to initiate a full synchronization of the products to rectify the 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 being used. In case of doubt, it is advisable to update the relevant modules.
- Specific errors related to EventBus may also occur, such as the inability to refresh an access token (error 452), a misconfiguration of the environment (error 453), or writing issues in the database (error 455). For these errors, it is generally necessary to check the server configuration, ensure that the access rights are correct, and that the modules are properly installed and up to date.
- Banning certain IP addresses may also block synchronization. The PrestaShop support can provide these addresses in case of doubt.
- To date, CloudSync is not compatible with the Alma payment module. If you are using Alma for payments on your PrestaShop store, it is therefore recommended not to activate CloudSync to avoid any malfunctions or data synchronization issues.
For any situation not resolved by these actions, please do not hesitate to contact PrestaShop support.