Support Article
Multiple timezones not supported for one calendar error
SA-26595
Summary
After cloning one dev environment to another, various operations encounter an error.
Error Messages
** Multiple timezones not supported for one calendar
Steps to Reproduce
- Create a new case.
- Observe the timezone error in the Pega tracer.
Root Cause
Perusing the instance list of "Records > organization > calendar" shows two different instances of the calendar named USDefault, one of which has a TIME ZONE column value of Los Angeles and the other is New York. This is disallowed. All calendars of the same name need to have use the same time zone.
Resolution
Delete the calendars using the incorrect time zone.
Tags:
Published December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.