@Sergei Baklan Thanks for the comment. Indeed, when I make a copy of the file it does work so there is a workaround. But for automation sake it would be nice to have it working via powerquery.
Unfortunately, I cannot give you a sample of the file. The strange this is that after some trials and error runs, we saw that when the scheduler is triggered early morning (7AM) the imported gives the error. However, when we trigger it again at say 11AM, the importer works, even though we haven't made a copy of some sort. The whole process is the same. Therefore, I am quite lost to what the cause could be, because if it is a difference in SAS vs. normal xlsx then it should happen all the time.
