Hi Pega Community,
I have encountered a discrepancy while configuring the Execution mode for Connect REST rules in Pega. When setting the Execution mode to “Execute asynchronously (queue for execution),” I faced an error due to the Request Processor configuration.
Issue Description:
When the Execution mode is set to “Execute asynchronous (queue for execution)” and the Request Processor is not configured, the system throws the following error: “Request Processor field must be blank when in ‘async’ execution mode.”
Discrepancy:
The error message appears to be incorrect. Based on the context, the error should correctly state: “Request Processor field must not be blank when in ‘async’ execution mode.”
Impact:
This discrepancy can lead to confusion for developers configuring Connect REST rules, especially since it has been unnoticed in version 24.1 as well.
Recommendation:
Please address this error message discrepancy in future updates. When working on this rule, developers should be cautious and ensure that the Request Processor field is correctly configured when setting the Execution mode to asynchronous.
Thank you for your attention to this matter. I look forward to any updates or workarounds the community might offer.
Thanks,
Mohammad Ravoof.
