Exception Handler Fails to Properly Reset

Products

• CA Process Automation Base
• Process Automation Manager

Issue/Introduction

My process contains several operators and an exception handler specifying what should happen next depending on the type of exception detected.  For example, if it is a System Error, or an Unidentified Response, or an Aborted operator task.  For some types of exceptions the process is ended, for other types of exceptions, data is collected and reported, and the process continues.

Consider the case where the exception is detected and the exception handler collects data and then continues the process. If a second exception is detected and it is an "Unidentified Response," we are finding that the second exception does not accurately reflect the name of the second operator that failed, but, instead, reports the second exception under the name of the first operator that failed before.

Additionally, if the exception handler ends with a "reset" or "skip," the exception operations are executed again before the operator that failed has been reset or skipped in the main process.

Environment

Process Automation v4.3 SP4 and up

Resolution

Even though the problem is reproducible, it is strongly recommended NOT to have unhandled responses in the PAM content.  It leads to processes going to a blocked state and drags down the overall impact on the performance of PAM when all the blocked instances consume the runtime database.