Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

No batch output class found for customer id errors in log files



Developer modified the existing offer flow to get the offer back in WAIT status, if a wrong answer was received. When developer ran the program, offers does not enter into the WAIT state, instead an error was observed in the log files. The response was received via HTTP request.

Error Messages

Error: No batch output class found for customer id <<CUSTOMER ID>> when looked up in the Interaction services

Steps to Reproduce


Root Cause

HTTP URL used to send the response to any offer was something like below:


The Offer name configured in the outbound HTTP was still referencing the old Offer. To invoke any response the Outbound and Inbound Offer name should be same.


Replacing the old Offer name with new Offer name in the HTTP URL used for sending responses has resolved the issue

Published January 31, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us