The root graph has to contain a subgraph. When the time is up, it does the action it should but the main graph and its children, except the lowest subgraph fail. The lowest subgraph finishes ok. This is how the bug manifests itself in my environment. The customer sees a little different scenario where some subgraphs are aborted instead of failed. Might be caused by different design. Ticket: https://clovercare.zendesk.com/agent/tickets/204915
Attached is the cascade of jobs and configuration containing scheduler and a listener I used to reproduce the issue. The scheduled job is turned off and has to be started manually from the Scheduling tab.