This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
When creating/saving Exception Dates
for Working Hours
configuration via the K2 Management site
, the date loads and saves incorrectly resulting in losing a day each time.
E.g. create an Exception Date:
Independence Day > July 4
When you save the change and load it again; it will now appear as:
Independence Day > July 3
If you added another Exception Date or hit "Finish" again, the next time the date will be loaded as:
Independence Day > July 2
A bug have been logged and will be addressed in a future update.
Please see the following workarounds:
1. Add or manage Exception Dates via K2 Workspace, as the date will be maintained correctly:
2. Edit/correct each Exception Dates prior to re-saving (hitting 'Finish') if usage of the K2 Management Site is necessary.