Follow up queue

It’s important to know that this job can cover multiple ‘original jobs’. This depends on the amount of exports in the given time range (frequency of queue status exports). Therefore it’s a good idea to always check error messages on the orignal job instance. This gives a better overview.

Status completed

Once Akeneo was finished exporting the job status will be set to ‘COMPLETED’. This means that all the data was exported successfully to Magento’s queue. It’s import to know that at this moment your product changes are NOT yet applied in Magento. Therefore the Magento queue need to run first. It’s the task of this job to check if Magento is already finished exporting or not, and provide you the necessary feedback.

Export steps

The queue export job was written as a follow-up job of the previous ‘Magento product export job’. It has the task to check when Magento is finished importing. After this import a few crucial tasks needs to be done. Therefor it’s important to automate this job trough the crontab of your Akeneo system (for example each 15 minutes). This job handles three export steps. These are:

  • Linking products to their parent - this step will link the simple products to their parent (configurable products). In this step the error messages of Magento will be printed. These messages are also stored on the original export job. You can click these error messages open to see for which store this error was thrown. Also the post data will be visible here.
  • Exporting product associations - will link the related, crosssell & upsell products if configured (association mapping).
  • Updating queue status - checks if all the queue items of a specific job are processed by Magento. If so, the job queue items will get the correct statuses.

Open queue jobs grid

Since the 6.0 connector version a new grid was added. This grid provides an overview of all the job executions which were not completed yet by Magento. In this grid you can download or stop the job for further processing. Check the problem solving page for more information.

Status waiting for external queue

Once Akeneo was finished exporting data to Magento a custom job status ‘WAITING FOR EXTERNAL QUEUE’ is assigned to export job. This means that all the data was exported successfully to Magento’s queue. It’s import to know that at this moment your product changes are NOT yet applied in Magento. Therefore the Magento queue need to run first. It’s the task of this job to check if Magento is already finished exporting or not, and provide you the necessary feedback.

Export steps

The queue export job was written as a follow-up job of the previous ‘Magento product export job’. It has the task to check when Magento is finished importing. After this import a few crucial tasks needs to be done. Therefor it’s important to automate this job trough the crontab of your Akeneo system (for example each 15 minutes). This job handles three export steps. These are:

  • Linking products to their parent - this step will link the simple products to their parent (configurable products). In this step the error messages of Magento will be printed. These messages are also stored on the original export job. You can click these error messages open to see for which store this error was thrown. Also the post data will be visible here.
  • Exporting product associations - will link the related, crosssell & upsell products if configured (association mapping).
  • Updating queue status - checks if all the queue items of a specific job are processed by Magento. If so, the job queue items will get the correct statuses and also the original job status will be changed from ‘waiting for external queue’ to ‘complete’