Hi, I’m facing an issue while publishing from Hiero using AYON. I have configured the reviewable to be generated from the EditRef, and the EditRefs that get exported always use the first shot of the EditRef instead of the specific shot I’m publishing for each shot.
Note: I’m not getting any error logs during the publish process.
Hi, I found the solution for the issue. It turned out that I had created a new staging directory, and all temporary files were being written there. However, the directory was not being cleaned after publishing processes completed. Because of this, the old temp files remained in the staging folder and were being reused, which I guess caused the same edit reference to be exported for multiple shots.
After clearing the staging directory, the edit references started exporting correctly for each shot (so no more exporting the same editRef for every other shot).
This still sounds fishy 
What would be the steps to reproduce? What did you have configured as custom staging dir? I assume it was set to be persistent?
I changed the staging directory from the default path because the default location was on the C drive , and when publishing large files a lot of temporary files were being generated there, which quickly filled up the storage.
To avoid this, I configured the custom staging directory to point to our project location on the server , where we have significantly more storage available.
However, I noticed that the temporary files created in this custom staging directory were not being cleared automatically . I suspect this might have caused the issue I encountered while publishing editRefs .
The situation was:
- I had one large edit containing multiple shots.
- The editRefs were cut per shot.
- Instead of publishing the correct editRef for each shot, the first shot’s editRef was being published for all shots .
I assumed that this happened because old temporary files accumulated in the staging directory , and those files were reused during subsequent publishes.
I’m not sure if the staging directory was set to persistent , as I did not find a configuration at the time that explicitly handled automatic cleanup of the temporary files.
Steps that might reproduce the issue:
- Change the staging directory from the default location to a custom path.
- Publish multiple shots that include editRefs and reviewables .
- Allow the staging directory to accumulate temporary files over multiple publishes.
- After some time, it may start reusing previous temporary files, which could lead to the behavior I observed.