Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It is critical that users monitor the failures / queued transactions by monitoring the following parts of the application.

Infonote
titleCritical monitoring areas to monitor

Client:

  1. Records waiting to upsync – Amber icon on the network connection status icon (tablet).  Accessible through Settings->Advanced Options->Show Queue.
  2. Failures – Red icon on the Sync Log icon.  Accessed by selecting the Sync Log icon and selecting “Failed” records from the drop down selection box.  If the “Fix record” button is available, you can correct data errors, otherwise, errors will need to be reported to your administrator.

Server:

  1. In recent servers, users can check Administrator->Monitoring where a summary of recent failures are listed.
  2. All errors can be checked in Queues->Delivery In.  Pending records are records queued for processing, others indicate some kind of failure.
    1. Records can be viewed (to see related records and fix failures) using the Edit Transaction icon
    2. Records that failed within the last 24 hours (controlled by system key queue.recordexpiretime.hours.short) will be reprocessed by the QueueJob, which is usually run every 30 minutes.
    3. Records that are resubmitted multiple times and still result in failures, will still remain in the queue but will be ignored after the 24 hour period by the short run queuejob.  It is unlikely that resubmitting them will result in a successful notification but if you wish for them to be reprocessed, further medium and long term queuejobs can be configured.
  3. In most cases, failures will require manual intervention before they can be processed.  Therefore, monitoring Delivery In for failures is critical.
  4. If failures repeatedly occur, it is usually due to missing validation on the client or missing fields.  These validation issues can be fixed with JavaScript scripts, to prevent errors occurring in the future.  Unless ownership is taken to prevent future errors, failures can re-occur frequently.
  5. The aim of the server administrator should be to ensure that the Delivery In queue is clear of any failed records, this is a pro-active role.

...