SLAs are not getting attached/cancelled when the conditions matched (start, cancel) on task recordsIssue When you raise/update any tasks (incident, case and etc), you notice: >> the SLAs are not getting attached when conditions matched >> the SLAs are not getting cancelled when cancel conditions matched. >> The flow used in the SLA definition was not executed (flow designer - executions) in the error logs, you could see below: *** Script [TaskSLAController]: 2024-02-15 18:31:30.544 runNow: error occurred during SLA processing of task INC1234567 com.snc.process_flow.exception.ProcessAutomationException: Failed to find complex object schema Similar error can be observed when you enable the SLA logging (TaskSLAFlow): 11:23:33.395 [TaskSLAFlow]: 2024-02-15 11:23:33.394 initialize: with task_sla e5da51b24714c610d441b7cd436d436b 11:23:33.396 [TaskSLAFlow]: 2024-02-15 11:23:33.395 start: copy of Flow 828f267973333300e289235f04f6a7a3 started for Priority 1 resolution (1 hour) 11:23:33.635 sys_id="31da51b24714c610d441b7cd436d439d" level="2" source_package="1907cc1047032110d441b7cd436d4319" source="com.glide.ui.ServletErrorListener" message="*** Script [TaskSLAController]: 2024-02-15 11:23:33.632 runNow: error occurred during SLA processing of task INC1234567 com.snc.process_flow.exception.ProcessAutomationException: Failed to find complex object schema CauseThe cause of the issue is due: 1. the flow which is used on the SLA definition is either inactive or broken - open the flow in the flow designer and you could see an error: "Your flow can not be found. Flow sys_id: 2. Custom flow attached to the SLA definition is run by user whom initiate the session. This should be changed to system user. Steps to check the flow: 1. Open the affected SLA definition 2. See the Flow value 3. Check in the flow designer if the flow is active and not broken 4. Check flow property if it is run by system user or user whom initiate the session.Resolution1. Export the same flow from any working instance (OOB - if they are using the Default SLA flow or custom flow from customer's instance.) using an update set. 2. Implement the update set 3. Make sure the flow is active and not broken after committing the update set. It should resolve the issue and the error is no longer observed.