CSV gets transformed into {"fileAccessToken":"ey..."} by AARI

​@Augustin That’s not an error -- that’s how a “File” variable is seen internally. 

The difficult part remains: determining what changed.

If you had this in production for more than a year, the original Process Composer was used to create the process. We are currently on Process Composer 2 (a.k.a., Mozart Composer). It handles files differently than the original Process Composer did. If the process was modified in PC2, it’s possible that caused some of the issues.

Updating a package used for the Task Bot linked in your Process could also cause some distress.

In PC1, files were passed from a Form to a Task Bot by passing the file object as an input to a file variable AND passing the file object as an input to a string variable. Then, in the Task Bot, you would use a String: Extract text to remove everything after ?fn= to get the filename passed.

In PC2, it’s almost the same thing, except when passing the file object for the filename (formerly to a string), you now cast it was a List variable. In the Task Bot, the String: Extract text is pretty much the same, except you use array element 0 of the list as your source.

Let us know if you can figure out what changed and caused this to happen… ‘cuz it’s gotta be something.

Hi Aaron,

Thanks for your very fast answer.

The root cause was the File storage location : it was set as Document Workspace Storage instead of Automation Co-Pilot Storage. (See screenshot)

It is really strange as nobody in my company seems to have changed it and there is no trace of recent modification in the control room history.

Hopefully the error was quickly resolved, without much inconvenience !