PO09032, WorkItem:272426 - Activate Share Set activity of the Advanced Evidence Sharing workflow is not correctly handling timeout exceptions
Issue Description:
When a transaction timeout occurs during the Activate Share Set activity of the Advanced Evidence Sharing workflow, the exception that is thrown is not correctly propagated to the infrastructure. This can cause the workflow activity to remain stuck at the 'In Progress' state.
Steps to Reproduce:
This issue occurs when the transaction for the Advanced Evidence Sharing workflow times out during the Activate Share Set activity. A number of underlying issues could cause a timeout to occur, including but not limited to:
- Network latency
- Database performance
- Volume of data
If a timeout happens for any reason during this particular workflow activity, then it will remain stuck in the 'In Progress' state.
Resolution:
The exception handling has been updated in the Activate Share Set logic to correctly handle transaction timeouts. These exceptions will now correctly propagate to the infrastructure and the workflow activity will be retried a number of times. If the activity continues to fail, it will be placed on the process instance error (PIE) queue.
Technical:
The Activate Share Set logic was attempting to catch any exceptions that occurred during the activation of shared evidence on a case. If evidence failed to activate, the system was updating the associated delivery plan status to 'Complete with fallback to in-edit' indicating that the evidence was shared successfully but was unable to be activated. The logic handling this was too generic, which led to it incorrectly catching timeout exceptions. The update to the logic now means that timeout transactions are properly handled and exceptions of this nature are correctly propagated to the infrastructure.
PO09064, WorkItem:272427 - Rework the Advanced Evidence Sharing Workflow to activate evidence on each target case in a share set in separate transactions
Issue Description:
When evidence from a source case is shared to multiple target cases, the Activate Share Set activity of the Advanced Evidence Sharing Workflow process is responsible for activating the evidence on each target case. If a transaction timeout occurs during the Activate Share Set activity before the evidence on each target case is activated, the workflow activity can remain stuck at the 'In Progress' state.
Steps to Reproduce:
This issue occurs when the transaction for the Advanced Evidence Sharing Workflow times out during the Activate Share Set activity. A number of underlying issues could cause a timeout to occur, including but not limited to:
- Network latency
- Database performance
- Volume of data
If a timeout happens for any reason during this particular workflow activity, then it will remain stuck in the 'In Progress' state.
Resolution:
This issue has been resolved by releasing an updated version of the Advanced Evidence Sharing Workflow. The updated workflow process will activate evidence on each target case in a separate transaction.
Technical:
The original workflow was designed to iterate through each target case that evidence was shared to and activate each case in a nested transaction. All of the nested transactions were contained inside a single workflow activity transaction and if this outer transaction timed out the remaining nested transactions that were not complete would fail and remain stuck in the 'In Progress' state. The updated workflow process changes this and instead of running many nested transactions within one workflow transaction, the new Activate Target Case Evidence activity now only operates on a single target case at a time. The updated workflow process now iterates through all target cases to execute each Activate Target Case Evidence activity in its own transaction.
Solutions
Income Support HCR
Income Support HCR
PO09380, WorkItem:270733 - Advanced Evidence Sharing is not logging the underlying stack trace if an unexpected failure occurs during a reflection call to the HCR apply changes logic
Issue Description:
HCR specific logic is used to apply changes to evidence within Insurance Affordability cases. As a result, it is necessary to use a reflection API to initiate the apply changes functionality. When an unexpected exception occurs during the activity in the Advanced Evidence Sharing workflow that attempts to automatically activate shared evidence on an Insurance Affordability target case, the underlying stack trace is not being logged by the reflection API call which is required to call the HCR specific apply changes logic.
User Interface Impact: No
Prerequisite(s):
An unexpected exception during the auto-activation of evidence on an Insurance Affordability integrated case is required to reproduce this issue.
Steps to Reproduce:
- Login as an Insurance Affordability caseworker.
- Register a person and submit a new application.
- Authorise the application.
- Navigate to the newly created integrated case.
- Issue: The evidence has been shared but is left in edit on the target case as the auto-activate failed with an unexpected exception and the underlying stack trace has not been logged.
Resolution:
The logic for handling unexpected exceptions during the reflection call has been updated to correctly log the underlying stack trace that caused the activation of evidence to fail.
