looking for advice on handling increased latency in our eu-west byoc deployment. the performance dashboard shows a spike in failed interactions, but the agent side reports no issues. when reviewing the conversation detail view, the status flips to ‘failed’ with an architect flow timeout error after exactly 30 seconds of silence. this correlates with the edge node location in frankfurt, which seems to have higher jitter today. the flow logic includes a gather input step with a 10-second timeout, followed by a set variable action. the issue appears when the input timeout is exceeded, causing the flow to hang before the error is logged. we are not using any api calls in this segment, so it is purely a flow execution issue. the business impact is significant as these calls are not being routed to the queue, skewing the service level metrics. how can we adjust the flow logic to handle edge latency without introducing artificial delays? also, is there a way to filter these specific timeout errors in the performance dashboard to exclude them from the abandonment rate? the current view lumps them with true abandonments, which distorts the kpi reporting for the regional managers.