Frames to Fix in Houdini re-rendering all frames again

Hi guys,

I have a question about how to correctly fix frames that were not rendered properly in Deadline. When we simply requeue our tasks to render and publish again, AYON gives an error during publishing, saying that there’s a version incompatibility between workfiles and the publish.

I think the correct way to do this is by using the “Frames to Fix” option in the publisher, right? But when I use it, AYON re-renders all the frames again (both the correct ones and the incorrect ones). Am I missing something in this process? How can I correctly fix only the problematic frames and publish a new version?

What version of the AYON core, deadline and houdini addons are you using? I’m pretty sure tweaks were done to this very recently:

Requiring e.g. ayon deadline 0.5.18 and core 1.6.5.

The exact workflow perhaps @mustafa_jafar may have some good doc links for though. :slight_smile:

We are using ayon deadline 0.5.17 and core 1.6.4 as you can see in the attached screenshot. Maybe we need to update our ayon deadline plugin?

Please update both and try again, yes.

I’m not we have documentation for it but overwriting last publish has two separate options in publisher UI.

Edit: We have some documentation Render Custom Frames but it was before introducing custom frame options.

Edit2: I’ve updated the Render Custom Frames section

Hey!

I am trying to figure out how to correctly fix bad frames. (I have checked the Render Custom Frames page linked)

I am facing 2 issues:

  1. I do not have the Frames to Fix option when using local rendering - not sure if normal or not?

  2. when using farm rendering + custom frame, it does correctly render the problematic frames, but then fails at publish:

2026-04-01 21:23:05:  0: STDOUT: ERROR:pyblish.plugin:Traceback (most recent call last):
2026-04-01 21:23:05:  0: STDOUT:   File "C:\Users\admin\AppData\Local\Ynput\AYON\dependency_packages\ayon_2510091624_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
2026-04-01 21:23:05:  0: STDOUT:     runner(*args)
2026-04-01 21:23:05:  0: STDOUT:   File "C:\Users\admin\AppData\Local\Ynput\AYON\addons\deadline_0.6.0\ayon_deadline\plugins\publish\global\extract_last_version_files.py", line 52, in process
2026-04-01 21:23:05:  0: STDOUT:     raise KnownPublishError(
2026-04-01 21:23:05:  0: STDOUT: ayon_core.pipeline.publish.publish_plugins.KnownPublishError: Multiple collections [] found.
2026-04-01 21:23:05:  0: STDOUT: Traceback (most recent call last):
2026-04-01 21:23:05:  0: STDOUT:   File "C:\Users\admin\AppData\Local\Ynput\AYON\dependency_packages\ayon_2510091624_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
2026-04-01 21:23:05:  0: STDOUT:     runner(*args)
2026-04-01 21:23:05:  0: STDOUT:   File "C:\Users\admin\AppData\Local\Ynput\AYON\addons\deadline_0.6.0\ayon_deadline\plugins\publish\global\extract_last_version_files.py", line 52, in process
2026-04-01 21:23:05:  0: STDOUT:     raise KnownPublishError(
2026-04-01 21:23:05:  0: STDOUT: ayon_core.pipeline.publish.publish_plugins.KnownPublishError: Multiple collections [] found.
2026-04-01 21:23:05:  0: STDOUT: !!! ERR: 2026-04-01 21:23:05,409 >>> { CLI-publish }: [ Failed ExtractLastVersionFiles: Multiple collections [] found. -- <FrameSummary file C:\Users\admin\AppData\Local\Ynput\AYON\addons\deadline_0.6.0\ayon_deadline\plugins\publish\global\extract_last_version_files.py, line 52 in process> ] 

I had all my v018 frames + 1v019 frame (the correct one) but didn’t manage to figure out how to publish a correct version without having to re-render everything, or publish by hand, etc.

What am I missing?
Thanks!

For Houdini, the plugin is enabled by this one in settings.

I’ll try to give it a try when possible.

1 Like

Kind of follow up question would be how do we publish frames that exist but for which the publish failed for some reason?

Frames are fine. Publish isn’t going through, how do I retry publishing using the same frames? Say I want to publish frames from v001 from scene v002.
In Houdini

image
and having a toggle “Rewrite past version” with a dropdown for the version number? Would that be an option that makes sense somehow?

Just an idea

Rewriting past version where you can specify the version explicitly.
I think it’s possible. One also may argue about having one setting for it. instead of having a farm option and local publishing option.

Could you make a request for it here.

1 Like