DomainSupport APIs give a incorrect domain following flow executionDescriptionDomainSupport APIs give a incorrect domain following flow executionSteps to Reproduce Install Domain Support plug-in (com.glide.domain.msp_extensions.installer) with demo dataThis will create 2 users http://<instance>/sys_user_list.do?sysparm_query=user_nameLIKEoceanic.employee%5EORuser_nameLIKEacme.employee&sysparm_view=Set all email event process Jobs (sys_trigger_list.do?sysparm_query=nameLIKEevents%20process) to Trigger Type = On DemandCreate 2 new sys_email records:1) User: 107c14341f1310005a3637b8ec8b7008 (acme.employee)Subject: Acme Email2) User: 3c7e94341f1310005a3637b8ec8b7029 (oceanic.employee)Subject: Oceanic EmailOn each record click the reprocess event UI action (This should not really process anything because we've disabled the handler jobs for email.read sysevents)Create a flow which is triggered upon incident creation with a log action (log any string). Make sure the flow runs in the foregroundActivate the flowGo back to http://<instance>/sys_trigger_list.do?sysparm_query=nameLIKEevents%20process%5Eparent!%3DNULL&sysparm_view= and set the trigger type to intervalThis should trigger the creation of 2 incidentsExpected: Acme Email incident is in the TOP/Acme domain, Oceanic Email is in the TOP/Oceanic AirlinesActual: Both incidents are created in the same domainWorkaroundSet:GlideTransaction.get().setAttribute("data_domain", null);GlideTransaction.get().setAttribute("process_domain", null);after each flow executes.Related Problem: PRB1453652