Troubleshooting
Learn how to resolve the most common problems people encounter with the Akeneo integration.
Last updated
Was this helpful?
Learn how to resolve the most common problems people encounter with the Akeneo integration.
Last updated
Was this helpful?
If you're encountering some oddities during the integration, here's a list of resolutions to some of the problems you may be experiencing. If you have any problems or requests, please contact .
Warning: The following features are only available since the 6.0 version and for SaaS customers.
Events are sent from your Akeneo instance to the middleware every time you create or update a product. The event's payload includes your product(s) metadata. In the context of the TextMaster integration, we use these events to detect when you selected product(s) you wish you send to translation.
The logs of these events can be found under the "Connect" → "Event logs" page.
If there are no events sent after you've sent product(s) for translation, your Akeneo instance is most likely not configured properly. Make sure you have configured the consumer worker correctly for the Events API to work. More information about this is available here:
You may see the following messages in your event logs:
ERROR The endpoint returned an error. In that case, the middleware received the event request, but something went wrong, and it answered with an error
ERROR The endpoint failed to answer under 500 ms. This error means that the middleware did not respond quickly enough
WARNING The maximum number of requests per hour has been reached. If you have this warning log, you might be interested in increasing your limit and scalability restrictions
Your content may not be sent correctly to TextMaster if you encounter this error (which will be reported to you by our teams in charge of your connection).
This error occurs when the AKENEO_PIM_URL environment variable does not match the expected Akeneo PIM URL. To resolve it, ensure that the AKENEO_PIM_URL variable is set to the correct URL as specified for the connector configuration.
To resolve this problem you need to:
Locate the AKENEO_PIM_URL environment variable in your configuration files.
Ensure the value of this variable aligns with the PIM URL configured for your connector, rather than a local development address (http://localhost:8080).
If the environment variable does not update, modify the argument directly in the Akeneo code configuration as a workaround. For example, update the pim_source argument in the relevant handler file to the correct PIM URL.
NOTICE The event was not sent because the product does not exist or the connection does not have the required permissions. When the PIM doesn't send an event because of a lack of permission, it can be normal. For instance, if you previously set up the connection permission to not receive events on products that are irrelevant for this particular app. If you think you should have received this event, please take a look at the
