CAB Agenda Tiimer and CAB Meeting Timer on CAB Workbench do not start from 0Issue Field types on CAB Workbench manifest the following behaviour:- CAB Agenda Item timer starts from 999 instead of 0- CAB Meeting timer does not start form 0 as it should if the start date/time is in the futureCause- CAB Agenda Item timer: field type of "Current agenda item start time" and "Current agenda item end time" on the table [cab_runtime_state_list] is not correct at database level.- CAB Meeting timer: field type of "actual_start" and "actual_end" on the [mtg_meeting] table is not correct at database level. The datatype of the above fields is of Date/Time type OOB, and was wrongly altered to Date type on the database.ResolutionChanging the field type of above mentioned fields from Date to DateTime field type on DB side resolves the issue.Related LinksDuring troubleshooting, checked and found out that the Widgets, client scripts, business rules, even sys_dictionary records were OOB version. Hence, checked at the DB level and found out the root cause of the issue.