Docs  /  App  /  NAVAX Replication  /  Working with the App

 Errors Caused by Replication Entries

2026/02/20 • 2 min. to read
Due to setup errors or special data constellations, a replication entry may receive the status Error when executing the replication. Such an entry causes the replication in the affected company to not be performed for all replication entries after the defective entry. If you have entries with the status "Error", there are several options to resolve this situation. This should only be done by an experienced BC user who also understands the database structures well. Among others, the following correction options are available:

• Fixing the cause of the error With each replication run, the system will attempt to replicate the record again. If the cause of the error is resolved, the replication will be performed normally.
• Set status to "Skipped" This replication entry will no longer be considered during replication and thus no longer blocks the replication. Please note that this entry has therefore not been replicated, which may lead to subsequent errors in individual cases. The replication itself automatically sets some entries to "Skipped". For example, when a record is to be deleted but no longer exists in this company. Or when a record is to be newly created but already exists in this company.
• Set status to "To check" This replication entry will no longer be considered during replication and thus no longer blocks the replication. You can review this entry at a later time and decide whether to skip or replicate it.
• Manually correct an invalid field value If, for example, an invalid field value in the details caused the error, you can also manually change this field value directly in the replication entry. On the next replication call, the replication will attempt to replicate this entry with the changed value.