@olivierlambert said: On your backup remote, look at the file left behind by the failed run It's empty I increased the schedule to every 30 min. All 3 of them are OK [image: 1783076106533-ddfcf1d5-bae9-4a7a-b45d-64ba131fe80c-image.jpeg]

Great! I think this is really the best possible approach to make it clean

@florent Sure, but I can only do it over the weekend. Also, I'll try to check if the script built the correct branch. First time using the script to build anything other than master. On a side note: recently some other strange errors started to show up "Body timeout Error". These are plain full backups to a remote with disaster recovery for another cluster, that always worked fine. Also, in this case, the timeout defined within the job doesn't cancel the job and the remaining jobs in the sequence don't run. Haven't had the time to dig into this - when I do, I'll start a new forum post. [image: 1783089319496-790bd845-1932-4f33-abfd-36441d720aa1-image.jpeg] Cheers, Pedro