<h2>No order found for request item : RITM0000XXXX error while provisioning using Cloud Template in a domain seperated Instance</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Description</h3><section><ul style="list-style-position: inside;"><li style="font-size: 11pt;"><span style="font-size: 11pt;">There is an AWS Cloud Formation Template and while trying to provision using the template, nothing is happening and RITM is showing "No order found for request item" message on the cloud user portal.</span></li></ul> <p style="padding-left: 80px;"><span style="font-size: 10pt;"><img style="border-style: solid; border-width: 2px;" src="sys_attachment.do?sys_id=479a61ed1b34e950546e35df034bcb57" alt="Pasted image.png" width="1000" height="361" /></span></p> <p style="padding-left: 80px;"> </p></section></div><div ><h3 >Cause</h3><section><ul style="list-style-position: inside;"><li style="font-size: 11pt;"><span style="font-size: 11pt;">After filling all the details in the template when the user click submit, it creates a request and Req Item at backend and it should trigger workflow.</span></li><li style="font-size: 11pt;"><span style="font-size: 11pt;">In the current impacted environment, it is observed that, there are 2 workflows; one for global and one for specific domain.</span></li></ul> <p style="padding-left: 80px;"><img style="border-style: solid; border-width: 2px;" src="sys_attachment.do?sys_id=154c29e11b74e950546e35df034bcb07" alt="Pasted image.png" width="1000" height="373" /></p></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li style="font-size: 11pt;"><span style="font-size: 11pt;">Officially we support Domain Separation from Orlando, but the "Blueprint Request" workflow is associated with "Global" this Workflow is not Domain Separated and this must need to be in Global Domain.</span></li><li style="font-size: 11pt;"><span style="font-size: 11pt;">Thus we recommend deleting workflow in other domain. <span style="text-decoration: underline;">In the impacted instance, we deleted the workflow and provisioning started working.</span></span></li></ul></section></div></article></div>