Errors in data processing are displayed in the administrative panel of the project.

A user with site administrator rights can view the status of job processing in the exchange queue.

To do this, go to the Exchange queue section

If an error occurs during the processing of any package, then the text of the error can be viewed by clicking on the number of package processing errors in the Synchronization errors column

On the page that opens, in the Messages section, the text of the error that occurred during the processing of the batch and the Type of object during the processing of which an error occurred will be displayed.

If there is an error in the 1C registration log related to the Agora exchange, then information about this error will be sent to the portal.
The error text will be displayed in the Synchronization errors section with the comment 1C error

Also, a user with Administrator rights can see all the errors that occur on the project in the Synchronization Errors section of the administrative panel

The page that opens will display the texts of all errors that occurred during processing, the date the error occurred, and the tasks within which the errors occurred.

Thus, a user with site administrator rights has the opportunity to receive information about errors that occur during the data loading process.
Below are examples of common errors and solutions to problems.

• 1C: Processing - Agora exchange module, additional loading at prices and balances.
• Portal: New synchronization errors in the exchange queue.

• Portal: Check the presence of a guide in external objects.

• 1C: exchange data package: along the path in the Basic settings of the module.
• Go to the exchange folder.

• We find the required package.
• Find the required guide in the code.

• Portal: We check the availability of this currency by Name - we find the Code.
• 1C: We check the code and the Symbol code of the currency that does not pass.

• Portal: We check the code and the Symbol code of the currency that does not pass.

• We perform additional data loading in the Agora exchange module.

Error from the client's side: A new product is uploaded from 1C to the portal, but not recorded.

To solve the problem, go to the Synchronization errors section of the administrative panel

When processing a batch, an error occurs when processing an object Internal category with the text: Unable to find object SupplierCategory with external ID d67f6bc2-cb54-11e6-adb3-305a3a56b5c5

The text of the error indicates that the package is unloading a product from the 1C category, which has not been previously uploaded to the portal.
To solve the problem, you need to upload the missing category to the portal.

Go to the exchange gateway and open the Agora processing data exchange setup

Select the Item Unloading Filter tab

Find the desired Item Group in the list
Select it and click the Unload Selected button

Check that the necessary data has been uploaded to the portal and the products have been registered.
It is possible to check the product record on the portal in the administrative panel in the Products section.

To analyze the problem, check the "Exchange queue" section of the portal in the admin panel.

Check if new packages are coming. This can be seen by the date of creation.

If packages are being downloaded, make sure that different packages are arriving and not the same one.

You can check this by the name of the packages.

If the same package is constantly loaded from 1C to the portal, then you need to check the registration log for errors.

To do this, go to "Processing" and select "Log".

Set the selection for Agora errors, as shown in the screenshot:

If the log contains errors of the "Object not found" type and the sending of one packet to the portal is looped, then this indicates that a deleted object has entered the change log.

To solve this problem, you must perform the following steps in 1C:

Go to the Agora exchange gateway, open the "Change registration for data exchange" processing

Specify the "AGORA" exchange node, if it is not specified

Expand the Directories branch and find in the directories objects specified as "object not found".

Click on each of them with the right mouse button and select the "Remove from registration" option in the context menu.

After that, check the exchange queue again on the portal. The portal should start receiving new packages.