Macro Input path randomly stopped working

[zachritter00]

I have an alteryx workflow I inherited that is used monthly for company metrics.  For the most part, I run a handful of reports, refresh xlsx and csv files in the input folders, run it, then refresh dashboards and spot check for inconsistencies.

I ran into something new today as I was trying to put data from a few months ago in to clear up some issues - I get an error at the macro:

Record #1: Tool #2: Unable to open file for read: C:\Users... and then my username, One Drive, and the file path

So I went into the macro, ran it, and the error occurred at the input tool, with Can't Find the File, with the entire path including my username, etc.

However, on the input tool in the macro under Connect a File or Database - it's just the direct path the the file from the directory the workflow and macro are in (down 2 folders then to the file)

I know the path is correct, I've copied it back over from explorer, but trying to refresh doesn't give me anything.  I thought it could be the file name (this macro is to aggregate a folder of files with a strange data structure), but that shouldn't matter, because right before the macro is a Formula tool that creates field FilePath as "\folder\"+[Filename]+"|||'Data Tab$'", so the filename should be irrelevant as long as the tabs are correctly named, which I've checked.

[dreldrel]

It is difficult to diagnose the issue without screenshots or the workflow, but the points below may help you identify the root cause.

1. Check if the files from a few months ago still exist in the file location.

2. If the files exist, check the file path passed into the macro. You can copy the file path produced by the Formula tool and test it in a brand new Input tool. If the new Input tool fails to read the file, the file path is likely incorrect.

3. If the file path is correct, review how the macro updates the path inside the Input tool. Depending on how the original designer configured it, the macro may update only file name, sheet name, or full file path.

Based on experience, the issue is most likely caused by the second or third point. Hope this helps you locate the underlying problem.