Since it's a flow being ran from the flow I'm working on, I'm not able to see the error code (Am I?)
If you run the flow from the console (not designer/debugging), then from the www portal/logs, there is no difference if you run the flow directly or via another flow.
Logs of the Desktop flows run from other desktop flows appear in the Power Automate web portal under "Monitor" -> Desktop flow runs. You can go there and look for failed flow to see errors.
I am having this issue as well! After putting the quotes around my variable name, I was able to get rid of the File type error but now the flow I was triggering stops working after it calls the file path location.
I don't know if I understand correctly what you are doing in both flows without seeing the code:
1. In the first flow, you use "File" actions to do some logic that produces a "file" object variable, and you pass that variable as an output variable.
2. In the second flow, you intend to take the Input variable holding the "file" object from flow one and use another "File" action to work on the file.
So if my understanding of the above is correct:
- Input variable error makes sense - You take the "file" object as an output variable from flow one as a "string" input variable in flow 2 - no go here
- After you added "to the output variable, you converted the output variable to a string, so flow 2 accepts it. But it is no longer a "file" object in flow two but a simple string. So you cannot do any "File" actions.
So, you would need to convert that "string" object into a "file" object again in flow 2 to be able to use "File" actions.
For example:
Flow 1:
Output variable 1: String with the folder where the file sits
Output variable 2: filename
Flow 2:
Get files in a folder and use path and filename to filter files, this will give you a variable of a "file" type, and you can use "files" actions.
Is that what you are looking for?
