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

Unable to create work object via agent, calendar exception



An Agent has been created in order to create WorkObjects using case management feature. The Activity used within the Agent configuration is running as expected outside the Agent processing (with a normal user), but not working when started by the Agent.
An error message is presented concerning unexpected Calendar

Error Messages

2015-03-06 12:07:55,602 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ ] (sinessCalendar.CalendarUtility) FATAL - Multiple timezones not supported for one calendar

Steps to Reproduce

No replication has been tried.

Root Cause

Data-Admin-Calendar instances could be added on many places. It could be added on the OperatorID, AccessGroup and of course WorkObject. But agent will not be having Calendar associated to and this where the confusion was coming from.


After having explained and identified which Calendar the system will be using at runtime, it has been decided to add the Calendar name at the WorkObject level using pyCalendar property.

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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