Hi all, I had a quick question about the python API call “get_workfiles_info”. I have been testing this out providing a project name and a task id, and I’ve observed that the call seems to only be returning a subset of the available workfiles for the task.
If I manually perform a save-as operation on a workfile, creating a new version, then that version of the workfile is returned by get_workfiles_info.
If, however, I perform a publish in the workfile, which also happens to version it up, this latest version is NOT returned by get_workfiles_info.
I’m wondering if this is a bug and if anyone else has come across this?
When I check the task on the server, it also only shows a handful of workfiles (but not all of the workfiles I have on disk). So I guess the API call is not really at fault, maybe the question is more “why do only some workfiles get registered on the server”.
Good point and I think this is actually bug because workfiles saved during the publish should behave the same.
We are in the middle of changing how workfile api works (on pipeline side at least) - see here:
Why some workfiles works and some not - it probably has something to do about api calls used to produce them. And that should be consistent and well documented.
