BrahmeswaraRao Member since 2016 37 posts
Posted: 4 years ago
Last activity: 4 years 9 months ago



We are getting following exception in our production logs. It's occurring while creating the work object via agent .

sinessCalendar.CalendarUtility) FATAL   - Multiple timezones not supported for one calendar.

I've gone through the  PDN article ,which is addressed the same issue as suggested to add the calendar at work object level by using pyCalendar property.

But in our case, unable to narrow down on root cause of the issue based on following factors.

1) Is WO  being committed to data base, despite of this exception occurs in logs?

2) I had verified couple of existing objects ,which were created by agent, and  I could see that the pyCalendar value is getting populated on work page.

    Do we have any scenario in which pyCalendar value could be missed on work page?

3)  In our App, we do have couple of other agents ,which creates the different work object,but we didn't see similar exception with them.

Please share your thoughts if you have work around to this.

System Administration
Moderation Team has archived post
Share this page LinkedIn