Multiple timezones not supported for one calendar error
After cloning one dev environment to another, various operations encounter an error.
** Multiple timezones not supported for one calendar
Steps to Reproduce
Create a new case.
Observe the timezone error in the Pega tracer.
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.
Delete the calendars using the incorrect time zone.