Google Drive Connectors; API response: File not found: <File ID>. (ToolId: xxx)

[Julia_Mathew]

I have a workflow that was deployed into production and it worked and ran properly during testing. It is now giving an error message on the Google drive output tools and input tools that the File ID is not found. I did not save the output using File ID and just file path and the existing file action was overwrite sheet. And the input file uses wildcard to pick up the file in the folder. What could be the reason for the error when nothing in the workflow has changed or the file name and folder path are the same

[dreldrel]

Could you please share the screenshots and the workflow if possible? This would help review the issue

[apathetichell]

How are you connecting to google drive? Are you using a json key? My hunch would be the server worker node cannot find (ie does not have access) the specific file (either the template/base file set up in the connection file or the file you are using as input/output).

[Julia_Mathew]

Attaching screenshots below but unfortunately cannot share the workflow. This also does not happen to all workflows just couple of them and it is using the same credentials connected through google drive OAuth token. All files are shared with the account and credentials are shared on server. I think the issue is that while saving the workflow the tool captures the google drive unique file ID instead of the file name and uses that to pull the file next month. Since we have different versions of the file every month it's not appropriately picking the right file 

[apathetichell]

So there's some nuance here and it ties into how Alteryx impletemend their workspace integration. fileID is the unique identifier and is what the tool should be looking for --- not filename. filename in google workspace is not unique --- and not a specific identifier. fileID is. having said that --- if the gcp service account has access to the fileID it should be able to find it and run it. That would create a situation where you run the old file/old data --- not a situation where you cannot access the file. File access/finding the file means either the file is deleted or the authenticated user cannot access it..