Hi all, we have a deployment which is served with “flow.serve()” within a kubernetes cluster. When this deployment is tiggered, either through an event/automation or directly with “run”, it stays in scheduled for exactly one hour before starting. As we are currently in UTC+01:00 here in Norway our main suspect is timezone-issues… But given the logs we can’t quite see where the error is… The container runs and reports it is uses CET+0100 when attaching onto it and getting date. We’ve tried to use the serve through CLI, and from code within the serve and setting the time zone there. Tried both UTC and Europe/Oslo. Both gives us one hour late runs. Your bot Marvin seems to think that the timezone setting in the CLI isn’t linked to any functionality. Just to clarify, we are not scheduling our runs. The deploy is to be ran when a specific event appears. We also try to start a quick run, but still 1 hour waiting time. If we do a custom run and set the start time to one hour ago then it’s picked up at once. Any suggestions?