Hi ,
Save not happening after Flow completion , it occurred 2 couple of times in production causing data loss. Not able to reproduce consistently.
Hi ,
Save not happening after Flow completion , it occurred 2 couple of times in production causing data loss. Not able to reproduce consistently.
Hope you are doing well.
Possible Causes:
Asynchronous Processing: The data may not have been saved immediately after the flow completed because the processing was asynchronous. In such cases, the data is saved in a temporary store and then flushed to the database later.
Transaction Handling: If the flow involved transactions and a rollback occurred, the changes made during the flow would not be saved.
Database Failures: If the database is unavailable or encountering errors, the save operation may fail.
Network Issues: Network connectivity issues can interrupt the save operation.
Memory or Resource Constraints: If the system is experiencing resource constraints or high memory usage, the save may fail.
Troubleshooting Steps:
Disable Asynchronous Processing: If possible, disable asynchronous processing for the affected flows to ensure immediate data saving.
Check Transaction Handling: Review the flow design and ensure that transactions are handled correctly.
Monitor Database Activity: Monitor the database logs to check for any errors or performance issues.
Ensure Network Connectivity: Verify that there are no network issues between the application and the database.
Monitor System Resources: Monitor the server’s memory and CPU usage to identify any resource bottlenecks.
Enable Error Logging: Configure error logging to capture any exceptions or error messages related to the save operation.
Use a Data Replication Tool: Consider using a data replication tool to create a real-time backup of the data, reducing the risk of data loss.
Recommendations:
Test Data Saving Thoroughly: Perform rigorous testing to verify that data is saved reliably under various conditions.
Implement a Retry Mechanism: Introduce a retry mechanism to handle temporary save failures and prevent data loss.
Review the Application Architecture: Evaluate the application architecture and identify any areas where asynchronous processing or transactions could potentially lead to data inconsistency.
Monitor the System Regularly: Monitor the system for any performance issues or resource constraints that could impact data saving.
Update the PEGA Platform: Ensure that the latest updates and patches for the PEGA Platform are applied to resolve any known bugs related to data saving.
I hope it helps.
Thanks
Megha
we are creating case in queue processor activity using pxcreatetopcase and flow is started but after 1st stage exection high level commit is not happening. After creating case there is no manual interaction required all are the utilities.