If you run showsourceversion activity and then pass in com.pega.pegarules.priv.businessCalendar.CalendarUtility, can you report the outcome? (module version string)? There are several hotfixes around the class, I would like to see where you at.
I think time zone come from operator ids/access groups. I believe you said this error only occurred on the agent, which has its own operator. Check there. Plus you should update that duplicate calender default record to reflect the time zone of the other one. This should make the multiple times zone error go away.
Regarding the business calendar error, I think there's a function in the system looking for a business calendar, find the function and see if it's calling a calendar instance that exists, or not.
I hope this helps.
Sent from my mobile phone. Please laugh at or excuse all errorneous auto-correction mistakes.
Thanks David, we got the root cause ,it looks like a bug in pega rules .
During creation of work object via agent, The calendar which is added at work object level by using pyCalendar is considered as business calendar ,and the same calendar is being used for goal/deadline time calculations,But the calendarname isn't passing properly(passing blank) to the new SLA structure when SLA instance is configured with pyEscalations and business days.
As if the calendar value is blank then @AddTime utility function takes the "Default" calendar instance which has been configured with two different time zones in our system.Hence causing below exception.
Multiple timezones not supported for one calendar
The business calendar object could not be found.
Capturing pyCalendar value.
Captured Calendar value hasn't been passed to new SLA structure