Safe to retry error while opening Records

This likely indicates that an Appian engine was too busy to handle the original request from the app server within a reasonable amount of time. As the error indicated, the request was safe to retry. So, as expected, once the necessary resources were freed up, and you retried, the request completed successfully.

I would recommend that you review the performance logs from the time that you encountered the error to see if there was an unusually high load on the system. Based on that information, it may be worthwhile to factor that amount of resource utilization into your application design and/or architecture.

It is also possible that, rather than generally high load on the system, there was a single operation (or set of operations) that took unusually long and monopolized the resources needed to complete the request. Again, reviewing the logs can help you determine if there was a problematic operation (such as a particular expression or node), and inform a decision about whether to optimize that operation, and/or add restrictions to limit potentially problematic scenarios.

For assistance investigating the issue in more detail, it may be helpful to create a Support Case. For guidance with the design and optimization of your application, you may want to consult Appian Professional Services.

This likely indicates that an Appian engine was too busy to handle the original request from the app server within a reasonable amount of time. As the error indicated, the request was safe to retry. So, as expected, once the necessary resources were freed up, and you retried, the request completed successfully.

I would recommend that you review the performance logs from the time that you encountered the error to see if there was an unusually high load on the system. Based on that information, it may be worthwhile to factor that amount of resource utilization into your application design and/or architecture.

It is also possible that, rather than generally high load on the system, there was a single operation (or set of operations) that took unusually long and monopolized the resources needed to complete the request. Again, reviewing the logs can help you determine if there was a problematic operation (such as a particular expression or node), and inform a decision about whether to optimize that operation, and/or add restrictions to limit potentially problematic scenarios.

For assistance investigating the issue in more detail, it may be helpful to create a Support Case. For guidance with the design and optimization of your application, you may want to consult Appian Professional Services.

Thanks Eliot. I will create support case