Hi, I can help you troubleshoot and stabilize this. From your explanation, it sounds like the split node time/timezone logic may either be failing globally or there’s an issue with how the timezone context is being evaluated after the recent fix.
I’ve worked on voice AI flows and routing logic before, including debugging conditional/split node behavior. If you want, send me screenshots of the current split node setup, timezone config, and a sample failed execution log I can help identify whether it’s a platform-side regression or a flow configuration issue and suggest a workaround quickly while support investigates further.
@Nicolas