|
|
|
•
|
Retry: This will attempt to process the transaction again. For example, you might select this option if the error message indicated that another user had the object locked. You can retry a transaction as many times as you want, but until the problem has been fixed in the main application, the transaction will continue to fail.
|
|
•
|
Accept: This indicates that you do not intend to fix the transaction. The transaction is marked as processed and flagged as failed. You might use this response, for example, for a transaction that failed because it was trying to cancel a task that had already been closed. Accepting failed transactions can lead to other failures, if following transactions depend on the failed transaction. This option should be used with caution.
|
|
•
|
Skip: This allows you to skip the transaction that is causing the error and move on to the next one. All other transactions for the same object will also be skipped. The status of the first skipped transaction changes to “correction required”. A user on the master APM application can try to fix the problem and resubmit it for processing. Skipping failed transactions can lead to other failures if following transactions depend on the skipped transaction. This course of action should be taken judiciously.
|
|
•
|
Skip all: This allows you to skip all remaining transactions and continue to the download step. The status of the skipped transaction changes to “correction required”. However, the status of all remaining transactions is left as “waiting to be processed” in the master APM application. These transactions can be manually submitted for processing. Otherwise, the next time you synchronize, the system will try to process all unprocessed transactions from the same remote computer. The drawback of this choice is that the downloaded data will not reflect the changes that were included in the skipped transactions.
|
|
•
|
Stop: This allows you to stop the synchronization process. This means that no new data will be downloaded to your computer. However, this does not undo the processing of upload transactions that has occurred up to this point. The status of the transaction that caused the error is set to “correction required”. The status of all remaining transactions is left as “waiting to be processed”.
|
|
