Workflow fails to create catalog task in RITM where as the activity state is in Running state.Issue The workflow creates the task in a TOP domain instead of the user's session domain.CauseThe workflow does create the task, but it is creating in the TOP domain rather than the domain where the request is raised.The behavior is caused due to the timer activity which is present in the workflow.All the configurations are correct, but if you look at the following BR: this looks for the "task_for" and "company" field's value and its domain and sets the domain of that task (sc_task is an extension of task table itself, so this BR executes)./nav_to.do?uri=sys_script.do?sys_id=b75b4e840a0a3c180111e05a3c158f15The task behavior created as expected in the other path where the task is created successfully because no timer activity is used switching the sessions. Tasks that are created after the timer in the workflow is hit, are created by system user whose company/domain is set to null/default, so the record gets created in global/default TOP domain.ResolutionYou need to set the values of "task_for" and "company" to the user that you desire it to be or company in the workflow activity "Create task" itself.