Utilizing 'expert_shell' wizard (to setup an on-call shift) causing high memory contentionIssue - We noticed high memory contention on a particular app node causing semaphore exhaustionCause - You went through semaphore exhaustion on particular app node because of high memory contention- You went through high memory contention when user 'user_1' was setting up an on-call shift using the /expert_shell wizard below: 2020-09-25 11:16:13 (461) Default-thread-15 EBC21F541B6F505CEBBFC9176E4BCB8C txid=87c6e75c1beb *** Start #40672227 /expert_shell.do, user: user_1 2020-09-25 11:19:20 (805) Default-thread-2 EBC21F541B6F505CEBBFC9176E4BCB8C txid=7c87e7141b2f #40675490 /xmlhttp.do Parameters ------------------------- sysparm_synch=true sysparm_scope=global sysparm_shift_repeats=weekly sysparm_shift_all_day=No sysparm_processor=ValidateSchedule sysparm_shift_end=10/05/202007:59:59 sysparm_want_session_messages=true sysparm_name=isValidNewSpan sysparm_sched_name=Test on-call schedule sysparm_sched_tz=US/Eastern sysparm_sched_group=12345678910111213141516171819202 sysparm_shift_start=09/28/2020 08:00:00 2020-09-25 11:19:20 (806) Default-thread-2 EBC21F541B6F505CEBBFC9176E4BCB8C txid=7c87e7141b2f *** Start #40675490 /xmlhttp.do, user: user_1 - What caused the high memory contention is that the user TYPED an incorrect date format on the shift_end section:User input date in the below format: sysparm_shift_end=10/05/202007:59:59 When it should've been in this format (space between date and time): sysparm_shift_end=10/05/2020 07:59:59 - The incorrect date format has confused the system and must've put it in an endless loop while calculating it that led to the high memory contentionResolution We recommend having users use the date time picker instead of manually typing the date to ensure the date is in the correct format and avoid another occurrence of high memory contention.