Buscar

What are the circumstances in which a CPM (synchronous or asynchronous) would enter an error state?

Environment:

Process Designer, Custom Process Model (CPM), Service Process Model (SPM)
All product versions

Resolution:

The blocklisting of a CPM occurs after the frequency of errors exceeds 60% for a short duration (100 seconds), or is erring consistently (greater than 35%) for an extended period of time without returning to an acceptable error rate (5%). The CPM will be prevented from running while in the error state, which lasts for 1 hour. After the hour passes, the CPM would start running again, but it will continue to show up in the Process Designer as being in an error state. If tested and deployed, the CPM status will change from Error back to OK. Also, if the CPM is tested and deployed while still in the 1 hour long error state, it will exit the error state.

To prevent a CPM from entering an error state, try catch blocks need to be added to ensure a graceful exit if an error does occur. Custom logging would log the error message to a log file that can be reviewed later. For more information about exception handling in ConnectPHP please review the documentation:
Answer ID 5169: Technical Documentation and Sample Code

For more details on adding custom logging to your CPM please review the following answer:
Answer ID 9897: Adding custom logging to your CPM