Why is there is a delay when a flow is triggered and when it is started?Issue A flow triggers on an event, but sometimes it takes up to 10 seconds before the flow eventually start. Why is this and how can this be improved?CauseYou can check the timing via the sysevent record. Look for flow.event and check the details. You'll see something like this: <process_on>2020-11-13 12:34:58</process_on><processed>2020-11-13 12:35:09</processed><sys_created_on>2020-11-13 12:34:58</sys_created_on> sys_created_on and processed_on are the moment the event was created, processed is the moment the flow is actually started. This latency depends on the event delegator which assigns events to nodes and then jobs on those nodes that pick them up. ResolutionIf the flow is configured to run synchronously, it will start automatically as it gets executed on the current user's thread. To do this go to the trigger and change it to run in foreground (by default it's running in the background).