Service Portal - How to solve "RangeError: Maximum call stack size exceeded" error while submission.Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms On Service Portal, when you click "Submit" on a Catalog item or Record Producer, it generates following in error in the console and the item doesn't get submitted. There are no errors in the logs, but only on the browser console: RangeError: Maximum call stack size exceededat canHideOrDisable (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64064)at canHideOrDisableContainer (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64076)at canHideOrDisable (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64066)at Object.set [as readonly] (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64191)at GlideForm.setReadOnly (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:58802)at Object.set [as readonly] (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64192)at GlideForm.setReadOnly (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:58802)at Object.set [as readonly] (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64192)at GlideForm.setReadOnly (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:58802)at Object.set [as readonly] (js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:64192)(anonymous) @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:12319(anonymous) @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:11029$apply @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:14813(anonymous) @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:17122dispatch @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:3003elemData.handle @ js_includes_sp.jsx?v=05-24-2018_1317&lp=Fri_Jun_15_21_36_00_PDT_2018&c=23_421:2877 Release Kingston Cause The cause of this issue is two "Container Start" type variables with same "Name". Resolution Remove one of the container start variables OR re-name them to different names.