Carts if not clearning for the user after the submission of the order guide.Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The user indicated that they were only trying to submit a single request, but hundreds of requests were generated each time. After investigation, it was observed that the cart for the user does not appear to be cleared out, causing all items in the cart to be submitted every time. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ALL Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } How the Checkout Process Works:When a user checks out their cart, a client–server interaction takes place. If the required functions and parameters are called correctly, the submission is successful and REQ and RITM records are created.During checkout, the following Script Includes are involved:• CatalogTransactionOrder ○ The execute() method checks for the sysparm_cart_name parameter. ○ If the parameter is empty, the DEFAULT cart is checked out; otherwise, the specified cart is submitted. ○ Once completed, it calls CatalogTransactionCheckout to finalize the order.• CatalogTransactionCheckout ○ This is the final step in the checkout process where REQ and RITM records are created. ○ If two-step checkout is enabled, the cart is not submitted immediately and the user is redirected to the initial checkout UI page (servicecatalog_checkout_one_v2).• CatalogTransactionCheckoutTwo ○ Invoked during the second step for instances using the two-step checkout model.• Finally, once cart.empty() is executed, the current user's Cart (sc_cart) and related Cart Items (sc_cart_item) are deleted. A new DEFAULT cart is then created when the user is redirected to the Order Status page. This summarizes the standard behavior followed during a Service Catalog checkout. - In this scenario the transaction is cancelled while running workflow associated to the RITM. - To resolve the issue, the transaction cancellation must be prevented so that cart.empty() can execute successfully and delete the current user's Cart (sc_cart) and associated Cart Items (sc_cart_item) records.To avoid transaction cancellation, please follow these steps:1. Delete all sc_cart records for the user.2. In the workflow, insert a Timer activity (set to 5 seconds) before the activity that is causing the transaction cancellation.3. Adding the Timer activity will split the transaction. This allows the cart transaction to complete successfully and ensures that the remaining workflow activities execute in the background.