Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Measurement Advisor Cloud Data Connector for AVEVA™ Enterprise SCADA

Retries and rejected records

  • Last UpdatedAug 07, 2024
  • 1 minute read

In the event of a failure to transfer data to the destination, the Raw Data Monitor application either retries the batch or reverts to row-by-row processing of the failed batch. The following table outlines errors and the resulting actions to retry:

Status

Action

FailedSQL

Revert to row-by-row.

NoPermission

Batch retry.

ConnectionTemporaryLost

Batch retry.

ConnectionClosed

Batch retry.

ConfigurationError

Batch retry.

RequestTimeout

Batch retry.

Where:

Row-by-row retry:

  • When the initial batch transfer fails, and the status indicates that the application will attempt row-by-row processing, the application sends the batch row-by-row. The system moves any failed row inserts to the rejected tables after the number of attempts has been exhausted. The number of row-by-row retries is defined via the MaxNumberOfRetriesPerRow key in the JSON file.

Batch retry:

  • The monitor process retries the transfer of a batch using up-to-the-configured number of batch retries as defined in the MaxNumberOfRetriesPerBatch key in the JSON file.

    Note: For information on overriding default configuration settings, refer to Modifying Configuration Settings.

  • If the batch is not successful, the application continues to send the batch until the underlying issue is resolved.

TitleResults for “How to create a CRG?”Also Available in