Support Article

Multiple timezones not supported for one calendar error



After cloning one dev environment to another, various operations encounter an error.

Error Messages

** Multiple timezones not supported for one calendar

Steps to Reproduce

  1. Create a new case.
  2. 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.


Delete the calendars using the incorrect time zone. 

Published August 9, 2016

Have a question? Get answers now.

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