Hi all

We move one of the processes to use the storage of a different Azure Account few days ago and the error that I reported has not happened again

I don´t think it was a coincidence so I conclude that the problem was related to some overload in the storage because I´m sure that our process don´t read and write the same file at the same time