This topic was automatically generated from Slack. You can find the original thread here.
Excited to try out the new File Stores functionality but am having a strange experience with the Google Drive - Download File action.
The action is supposed to download a file from Google Drive to the PD /tmp path, and the action claims to succeed, but any attempt to read (the file, a dir, etc) in a follow up action continually returns nothing (no files, no directories). Feels like I’m missing a key step.
Can share the wf if necessary.
It seems like the download “times out” if you’re in the builder for a little while.
Sometimes, I have to test the download action again for the file to be there.
But once deployed, there are no issues.
Actually, it may be that the Google Drive action is failing entirely. I tried removing the subdir in the destination file path and now that action won’t complete
Error
EROFS: read-only file system, open '1_16812377377_43x54_Window_PERF.pdf'
Still in /tmp, right?
It’s the only path we can write to.
Well I am assuming that tmp is hardcoded to the front of all Google Drive actions now, based on:
(line 39)
This is deployed & working in production:
Yeah I’m editing it now so that’s no longer the latest
I can save and publish this if it helps
ah, I see.
Well, maybe there’s a bug in the latest version 
Oh wait, are you using this?
Use this instead:
