Feature requests
Allow regex customization for folder entity names
We want to ban users from creating assets with leading digits (e.g. 01_character_A). Ayon currently is missing controls for this on the backend, would be great to add regex options.
Alex Szabados
💡
Allow regex customization for folder entity names
We want to ban users from creating assets with leading digits (e.g. 01_character_A). Ayon currently is missing controls for this on the backend, would be great to add regex options.
Alex Szabados
💡
Feature requests
Duration Attribute
I’d like to have a field that is calculated from the start and end date of a task. I couldn’t find a way to do this though. Is this possible?
Andy Gill 5 days ago
❓
Questions
Duration Attribute
I’d like to have a field that is calculated from the start and end date of a task. I couldn’t find a way to do this though. Is this possible?
Andy Gill 5 days ago
❓
Questions
Different date formats
I was wondering if it is at all possible to change the formatting of dates are displayed on the server? We are used to different formatting for readability and I'm wondering if its configurable.
Andy Gill
💡
Feature requests
Different date formats
I was wondering if it is at all possible to change the formatting of dates are displayed on the server? We are used to different formatting for readability and I'm wondering if its configurable.
Andy Gill
💡
Feature requests
Gantt Chart and Due/Startdate Desync
Hi! It seems like when I set start and end dates on tasks, it does not trigger the gantt chart to update. https://gyazo.com/57cdd62deefc3d26b05a01980012e379
Andy Gill
🐛
Bugs
Gantt Chart and Due/Startdate Desync
Hi! It seems like when I set start and end dates on tasks, it does not trigger the gantt chart to update. https://gyazo.com/57cdd62deefc3d26b05a01980012e379
Andy Gill
🐛
Bugs
Mandatory Message for Settings Changes
inspired by https://feedback.ayon.app/p/per-bundle-note-or-description When users are changing settings (either studio-wide or per-project) I’d love to require a little message asking for the reason of this settings update. Basically a commit message for settings changes. This message should be part of `bundle.updated` event’s payload. Usecase: We’re running a service that tracks all AYON studio settings with git in order to know who changed what when and also to be able to revert settings more easily. With this I would also be able to know why it was changed.
Tony Dorfmeister
Production
+1
💡
Feature requests
Mandatory Message for Settings Changes
inspired by https://feedback.ayon.app/p/per-bundle-note-or-description When users are changing settings (either studio-wide or per-project) I’d love to require a little message asking for the reason of this settings update. Basically a commit message for settings changes. This message should be part of `bundle.updated` event’s payload. Usecase: We’re running a service that tracks all AYON studio settings with git in order to know who changed what when and also to be able to revert settings more easily. With this I would also be able to know why it was changed.
Tony Dorfmeister
Production
+1
💡
Feature requests
AYON Publisher issues with Mac Intel processor
We have experienced problems when using the publisher on mac machines with intel processors. Logs show dependency packages issues with the specific architecture (arm64 vs x86_64). Is there a version of the app that would work with these machines ? How do we go about it ? Thanks.
Nikolaos Maragkos
Production
+1
💡
Feature requests
AYON Publisher issues with Mac Intel processor
We have experienced problems when using the publisher on mac machines with intel processors. Logs show dependency packages issues with the specific architecture (arm64 vs x86_64). Is there a version of the app that would work with these machines ? How do we go about it ? Thanks.
Nikolaos Maragkos
Production
+1
💡
Feature requests
JPG vs JPEG
inconsistency in format name causing render/publishing errors when rendering JPG in Blender. …\addons\blender\1.1.6\private\client\ayon_blender\api\render_lib.py https://community.ynput.io/t/blender-jpeg-vs-jpg/3222 getting this error when publishing: * `ValidateExpectedFiles` does a string-exact filename comparison * Expected: `...Beauty1001.jpeg` * Actual on disk: `...Beauty1001.jpg` def set_render_format(ext: str, multilayer: bool): """Set Blender scene to save render file with the right extension""" bpy.context.scene.render.use_file_extension = True image_settings = bpy.context.scene.render.image_settings if lib.get_blender_version() >= (5, 0, 0): if multilayer: image_settings.media_type = "MULTI_LAYER_IMAGE" else: image_settings.media_type = "IMAGE" if ext == "exr": file_format = "OPEN_EXR_MULTILAYER" if multilayer else "OPEN_EXR" image_settings.file_format = file_format elif ext == "bmp": image_settings.file_format = "BMP" elif ext == "rgb": image_settings.file_format = "IRIS" elif ext == "png": image_settings.file_format = "PNG" elif ext == "jpeg": image_settings.file_format = "JPEG" elif ext == "jp2": image_settings.file_format = "JPEG2000" elif ext == "tga": image_settings.file_format = "TARGA" elif ext == "tif": image_settings.file_format = "TIFF" ## def get_file_format_extension(file_format: str) -> str: """Convert Blender file format to file extension.""" # TODO: Figure out if Blender has a native way to convert to extensions if file_format == "OPEN_EXR_MULTILAYER": return "exr" elif file_format == "OPEN_EXR": return "exr" elif file_format == "BMP": return "bmp" elif file_format == "IRIS": return "rgb" elif file_format == "PNG": return "png" elif file_format == "JPEG": return "jpeg" elif file_format == "JPEG2000": return "jp2" elif file_format == "TARGA" or file_format == "TARGA_RAW": return "tga" elif file_format == "TIFF": return "tif" # Blender 5+ elif file_format == "CINEON": return "cin" elif file_format == "DPX": return "dpx" elif file_format == "WEBP": return "webp" elif file_format == "HDR": return "hdr" else: raise ValueError(f"Unsupported file format: {file_format}")
OCUDA
Pipeline
+1
💡
Feature requests
JPG vs JPEG
inconsistency in format name causing render/publishing errors when rendering JPG in Blender. …\addons\blender\1.1.6\private\client\ayon_blender\api\render_lib.py https://community.ynput.io/t/blender-jpeg-vs-jpg/3222 getting this error when publishing: * `ValidateExpectedFiles` does a string-exact filename comparison * Expected: `...Beauty1001.jpeg` * Actual on disk: `...Beauty1001.jpg` def set_render_format(ext: str, multilayer: bool): """Set Blender scene to save render file with the right extension""" bpy.context.scene.render.use_file_extension = True image_settings = bpy.context.scene.render.image_settings if lib.get_blender_version() >= (5, 0, 0): if multilayer: image_settings.media_type = "MULTI_LAYER_IMAGE" else: image_settings.media_type = "IMAGE" if ext == "exr": file_format = "OPEN_EXR_MULTILAYER" if multilayer else "OPEN_EXR" image_settings.file_format = file_format elif ext == "bmp": image_settings.file_format = "BMP" elif ext == "rgb": image_settings.file_format = "IRIS" elif ext == "png": image_settings.file_format = "PNG" elif ext == "jpeg": image_settings.file_format = "JPEG" elif ext == "jp2": image_settings.file_format = "JPEG2000" elif ext == "tga": image_settings.file_format = "TARGA" elif ext == "tif": image_settings.file_format = "TIFF" ## def get_file_format_extension(file_format: str) -> str: """Convert Blender file format to file extension.""" # TODO: Figure out if Blender has a native way to convert to extensions if file_format == "OPEN_EXR_MULTILAYER": return "exr" elif file_format == "OPEN_EXR": return "exr" elif file_format == "BMP": return "bmp" elif file_format == "IRIS": return "rgb" elif file_format == "PNG": return "png" elif file_format == "JPEG": return "jpeg" elif file_format == "JPEG2000": return "jp2" elif file_format == "TARGA" or file_format == "TARGA_RAW": return "tga" elif file_format == "TIFF": return "tif" # Blender 5+ elif file_format == "CINEON": return "cin" elif file_format == "DPX": return "dpx" elif file_format == "WEBP": return "webp" elif file_format == "HDR": return "hdr" else: raise ValueError(f"Unsupported file format: {file_format}")
OCUDA
Pipeline
+1
💡
Feature requests
I would like tasks to publish updates to kitsu
OK after a little post on the communities this appears to be not just me. Publishing anything from tray publisher - kitsu works, model families, look dev, whatever. However publishing a model / look dev update from the maya publisher doesn’t update in kitsu. Personally I’d rather not be using kitsu at all but the studio are sticking with it. Currently publishing reviews from Maya - Ayon - Kitsu works fine. Mainly it’s models, I want kitsu to change status and show a thumbnail and comment when a user publishes a model.
Playground user 2513
Pipeline
+1
💡
Feature requests
I would like tasks to publish updates to kitsu
OK after a little post on the communities this appears to be not just me. Publishing anything from tray publisher - kitsu works, model families, look dev, whatever. However publishing a model / look dev update from the maya publisher doesn’t update in kitsu. Personally I’d rather not be using kitsu at all but the studio are sticking with it. Currently publishing reviews from Maya - Ayon - Kitsu works fine. Mainly it’s models, I want kitsu to change status and show a thumbnail and comment when a user publishes a model.
Playground user 2513
Pipeline
+1
💡
Feature requests
Sorting by Folder Name does not work on overview page when grouping by folder
Here's an example. If you're grouping by Folder it actually sorts the Folder/Task colum, which is not the parent folder column that we'd want to sort on the left. No matter what I do, sorting the Folder column only changes the sorting on Folder / Task.
Dieuwer Feldbrugge
1
Production
+1
🐛
Bugs
Sorting by Folder Name does not work on overview page when grouping by folder
Here's an example. If you're grouping by Folder it actually sorts the Folder/Task colum, which is not the parent folder column that we'd want to sort on the left. No matter what I do, sorting the Folder column only changes the sorting on Folder / Task.
Dieuwer Feldbrugge
1
Production
+1
🐛
Bugs
Payload.mp4 when downloading files is confusing clients a lot
Hey there, When using Review ( or generally looking at reviewables and wanting to retrieve the original reviewable ) we need clients ( not logged in guests, this is already shielded correctly ) to be able to fetch the reviewables from the viewport. This currently works, BUT the file is renamed to a generic payload.mp4. Causing a mess. I want to suggest to keep the original name of the uploaded reviewable here, so our own naming keeps things sensible/tidy. I'd say this is quite essential for a clean workflow Thanks :)
Dieuwer Feldbrugge
1
Production
+1
💡
Feature requests
Payload.mp4 when downloading files is confusing clients a lot
Hey there, When using Review ( or generally looking at reviewables and wanting to retrieve the original reviewable ) we need clients ( not logged in guests, this is already shielded correctly ) to be able to fetch the reviewables from the viewport. This currently works, BUT the file is renamed to a generic payload.mp4. Causing a mess. I want to suggest to keep the original name of the uploaded reviewable here, so our own naming keeps things sensible/tidy. I'd say this is quite essential for a clean workflow Thanks :)
Dieuwer Feldbrugge
1
Production
+1
💡
Feature requests
Predefined/Enumerated Task Names/Labels
I would like to configure a project with the allowed tasks ahead of time and then whenever a task is created, it must be one of the tasks provided on this list. These tasks should continue to be sorted by task type (e.g. fx_fire is an fx task type). I would like the task project definitions to be first class citizens so that I can query the project configuration or the shot configuration of a particular task. I have plans to tie tasks/task categories into the layering order of our USD workflow and this will then tie into that potentially. You can think of the tasks as assets and a shot task as being an instance of that asset, if you like. If it is too much of a burden to create tasks on the project first, before making them in shots, you could potentially make a mode that will author a new project task from the same dialog for certain permission types. I want to eliminate areas where artists or coordinators need to enter strings by hand. At scale it is a virtual guarantee that we end up with slight deviations in spelling (tire_burnout or tyre_burnout), or spaces (spiderwebs or spider_webs), or capitalization (SpiderWebs or Spiderwebs). These inconsistencies make it much more challenging to build automation templates or track same-things across/between projects for forecasting the cost of certain tasks. Discord conversation here: https://discord.com/channels/517362899170230292/1528631102762127490/1530456273873797151 Thanks Ben
Ben Andersen
4
Pipeline
+1
💡
Feature requests
Predefined/Enumerated Task Names/Labels
I would like to configure a project with the allowed tasks ahead of time and then whenever a task is created, it must be one of the tasks provided on this list. These tasks should continue to be sorted by task type (e.g. fx_fire is an fx task type). I would like the task project definitions to be first class citizens so that I can query the project configuration or the shot configuration of a particular task. I have plans to tie tasks/task categories into the layering order of our USD workflow and this will then tie into that potentially. You can think of the tasks as assets and a shot task as being an instance of that asset, if you like. If it is too much of a burden to create tasks on the project first, before making them in shots, you could potentially make a mode that will author a new project task from the same dialog for certain permission types. I want to eliminate areas where artists or coordinators need to enter strings by hand. At scale it is a virtual guarantee that we end up with slight deviations in spelling (tire_burnout or tyre_burnout), or spaces (spiderwebs or spider_webs), or capitalization (SpiderWebs or Spiderwebs). These inconsistencies make it much more challenging to build automation templates or track same-things across/between projects for forecasting the cost of certain tasks. Discord conversation here: https://discord.com/channels/517362899170230292/1528631102762127490/1530456273873797151 Thanks Ben
Ben Andersen
4
Pipeline
+1
💡
Feature requests
"Project Root Not found" Pop UP
For artists especially remote ones, they may have the shared storage mounted under a different letter. And sometimes, they are clueless that they need to go to roots tab under project settings on the server. I wonder if this can be easily detected at earlier time. E.g. when they select a folder in the the launcher, the launcher can check if the roots exist. if not it can prompt them to pick the correct location for them. which will be set as a root override. THIS IS A MOCKUP.. This can potentially save some frustration for remote artists.
Mustafa Zaky Jafar
1
Community
+1
💡
Feature requests
"Project Root Not found" Pop UP
For artists especially remote ones, they may have the shared storage mounted under a different letter. And sometimes, they are clueless that they need to go to roots tab under project settings on the server. I wonder if this can be easily detected at earlier time. E.g. when they select a folder in the the launcher, the launcher can check if the roots exist. if not it can prompt them to pick the correct location for them. which will be set as a root override. THIS IS A MOCKUP.. This can potentially save some frustration for remote artists.
Mustafa Zaky Jafar
1
Community
+1
💡
Feature requests
PowerPack Sync Statuses (Studio level) ignores custom Anatomy Presets
At the Studio Settings level, the PowerPack Sync Statuses feature only pulls status options from the built-in/default Anatomy Preset. It doesn't read from a custom Anatomy Preset that's been created and set as primary in the studio. Steps to reproduce: Create a custom Anatomy Preset with custom statuses and set it as the studio's primary preset. Go to Studio Settings → PowerPack → Sync Statuses. Search for a status to use in a sync rule. Expected: The status search/dropdown should include statuses from the active custom Anatomy Preset (or at least the primary preset), not just the built-in default. Actual: Only the built-in default preset's statuses appear, with no way to change the source preset. Impact: Studios using custom status pipelines can't build Studio-level sync rules that reference their own statuses — they're forced to duplicate the setup at the Project level for every project, which defeats the purpose of a studio-wide rule. Suggested fix: Either let Studio-level Sync Statuses pull from the primary Anatomy Preset (whichever is currently set), or add a setting to choose which preset the Studio-level rules should read from.
#youssef#
2
Production
💡
Feature requests
PowerPack Sync Statuses (Studio level) ignores custom Anatomy Presets
At the Studio Settings level, the PowerPack Sync Statuses feature only pulls status options from the built-in/default Anatomy Preset. It doesn't read from a custom Anatomy Preset that's been created and set as primary in the studio. Steps to reproduce: Create a custom Anatomy Preset with custom statuses and set it as the studio's primary preset. Go to Studio Settings → PowerPack → Sync Statuses. Search for a status to use in a sync rule. Expected: The status search/dropdown should include statuses from the active custom Anatomy Preset (or at least the primary preset), not just the built-in default. Actual: Only the built-in default preset's statuses appear, with no way to change the source preset. Impact: Studios using custom status pipelines can't build Studio-level sync rules that reference their own statuses — they're forced to duplicate the setup at the Project level for every project, which defeats the purpose of a studio-wide rule. Suggested fix: Either let Studio-level Sync Statuses pull from the primary Anatomy Preset (whichever is currently set), or add a setting to choose which preset the Studio-level rules should read from.
#youssef#
2
Production
💡
Feature requests
Planner 1.0.0 - "Show Planner" toggle broken - missing /api/views/ endpoint (404)
Body: Summary The "Show planner" toggle in the Scheduler view does nothing. Both the right-click context menu option and the P keyboard shortcut fail silently. Environment AYON Server: 1.15.11+202607031715 (latest) Planner Addon: 1.0.0 Browser: Chrome OS: Windows Steps to Reproduce Open a project in the Scheduler view Right-click on the timeline → click "Show planner" Nothing happens — the planner panel does not appear Console Errors Two errors appear in DevTools console: 1. API endpoint not found: GET http://link/api/views/scheduler/base? 404 (Not Found) 2. Settings update blocked: updateViewSettings: no settings baseline available, aborting to prevent data loss. Call stack: command (SchedulerRemote-B3whaLuu.js:80) → LicenseWrapper-blS_677C.js:28 → updateViewSettings (WithViews-BQrbuIVR.js:1) → aborts Root Cause The Planner 1.0.0 addon's frontend uses the Views API (/api/views/scheduler/base) to load a settings baseline when the Scheduler page loads. This endpoint returns 404 on AYON Server 1.15.11 because the /api/views/ API does not exist yet on the server. Without the baseline, the updateViewSettings function in the core frontend (WithViews-BQrbuIVR.js) refuses to save any setting changes as a safety measure, which means the planner toggle cannot be persisted and the panel never appears. The addon's package.py declares ayon_server_version = ">=1.14.0", but the addon actually requires a server version that includes the /api/views/ endpoint. Expected Behavior Clicking "Show planner" should toggle the planner panel above the scheduler timeline. Suggested Fix Either: The AYON server needs to ship the /api/views/ API endpoint, or The Planner addon needs to handle the 404 gracefully and fall back to localStorage or default settings
#youssef#
2
Production
🐛
Bugs
Planner 1.0.0 - "Show Planner" toggle broken - missing /api/views/ endpoint (404)
Body: Summary The "Show planner" toggle in the Scheduler view does nothing. Both the right-click context menu option and the P keyboard shortcut fail silently. Environment AYON Server: 1.15.11+202607031715 (latest) Planner Addon: 1.0.0 Browser: Chrome OS: Windows Steps to Reproduce Open a project in the Scheduler view Right-click on the timeline → click "Show planner" Nothing happens — the planner panel does not appear Console Errors Two errors appear in DevTools console: 1. API endpoint not found: GET http://link/api/views/scheduler/base? 404 (Not Found) 2. Settings update blocked: updateViewSettings: no settings baseline available, aborting to prevent data loss. Call stack: command (SchedulerRemote-B3whaLuu.js:80) → LicenseWrapper-blS_677C.js:28 → updateViewSettings (WithViews-BQrbuIVR.js:1) → aborts Root Cause The Planner 1.0.0 addon's frontend uses the Views API (/api/views/scheduler/base) to load a settings baseline when the Scheduler page loads. This endpoint returns 404 on AYON Server 1.15.11 because the /api/views/ API does not exist yet on the server. Without the baseline, the updateViewSettings function in the core frontend (WithViews-BQrbuIVR.js) refuses to save any setting changes as a safety measure, which means the planner toggle cannot be persisted and the panel never appears. The addon's package.py declares ayon_server_version = ">=1.14.0", but the addon actually requires a server version that includes the /api/views/ endpoint. Expected Behavior Clicking "Show planner" should toggle the planner panel above the scheduler timeline. Suggested Fix Either: The AYON server needs to ship the /api/views/ API endpoint, or The Planner addon needs to handle the 404 gracefully and fall back to localStorage or default settings
#youssef#
2
Production
🐛
Bugs
Blender review removes camera backplates
Looks like the review camera’s object gets filtered out in the playblast review process. Resulting from any back plate that is on the camera gets hidden during the review process too. "show_overlays": true - in extract playblast preset, doesn’t appear to have any effect on image plates being shown or not. Thinking the applied_view() view function needs to explicitly add the review camera to the objects list to not isolate it, or "CAMERA" type needs to be added to this types var types = {"MESH", "GPENCIL"} objects = [obj for obj in window.scene.objects if obj.type in types]
Tommy Ford
1
Pipeline
🐛
Bugs
Blender review removes camera backplates
Looks like the review camera’s object gets filtered out in the playblast review process. Resulting from any back plate that is on the camera gets hidden during the review process too. "show_overlays": true - in extract playblast preset, doesn’t appear to have any effect on image plates being shown or not. Thinking the applied_view() view function needs to explicitly add the review camera to the objects list to not isolate it, or "CAMERA" type needs to be added to this types var types = {"MESH", "GPENCIL"} objects = [obj for obj in window.scene.objects if obj.type in types]
Tommy Ford
1
Pipeline
🐛
Bugs
Powerpack Status sync from folder to tasks
Sunrise would find it helpful if an ‘Omit’ status set by a producer on a shot folder would automatically set the children tasks to Omit as well. This is so that artists in their kanban view can see their assigned shot/asset task in Omit, and know not to waste time on it anymore.
Kevin van den Oever
💡
Feature requests
Powerpack Status sync from folder to tasks
Sunrise would find it helpful if an ‘Omit’ status set by a producer on a shot folder would automatically set the children tasks to Omit as well. This is so that artists in their kanban view can see their assigned shot/asset task in Omit, and know not to waste time on it anymore.
Kevin van den Oever
💡
Feature requests
Batchdelivery addon with ModuleNotFoundError for lablib on farm
The “extract_ocio_config_publishing” plugin from the batchdelivery tool is producing a ModuleNotFoundError on Deadline: 2026-06-30 19:46:49: 0: STDOUT: *** Failed to load 1 files 2026-06-30 19:46:49: 0: STDOUT: - C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\batchdelivery_0.4.3\ayon_batchdelivery\plugins\publish\extract_ocio_config_publishing.py 2026-06-30 19:46:49: 0: STDOUT: ********** 2026-06-30 19:46:49: 0: STDOUT: Traceback (most recent call last): 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\core_1.9.7\ayon_core\pipeline\publish\lib.py", line 403, in publish_plugins_discover 2026-06-30 19:46:49: 0: STDOUT: module = import_filepath( 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\core_1.9.7\ayon_core\lib\python_module_tools.py", line 45, in import_filepath 2026-06-30 19:46:49: 0: STDOUT: module_loader.exec_module(module) 2026-06-30 19:46:49: 0: STDOUT: File "", line 850, in exec_module 2026-06-30 19:46:49: 0: STDOUT: File "", line 228, in callwith_frames_removed 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\batchdelivery_0.4.3\ayon_batchdelivery\plugins\publish\extract_ocio_config_publishing.py", line 19, in 2026-06-30 19:46:49: 0: STDOUT: import lablib 2026-06-30 19:46:49: 0: STDOUT: ModuleNotFoundError: No module named 'lablib' It looks like lablib is shipped with the addon itself and not part of the dependency package. However, this error does not seem to have a negative effect on the deadline job, in this case a farm publish from nuke. I guess it has something to do with the fact that the sys path is modified on_host_install and therefore not being executed during a headless publish session on deadline. Maybe this can be handled in a nicer way so we avoid the ModuleNotFoundError? Or is this probably causing issues elsewhere?
Sebastian Brandhuber
🐛
Bugs
Batchdelivery addon with ModuleNotFoundError for lablib on farm
The “extract_ocio_config_publishing” plugin from the batchdelivery tool is producing a ModuleNotFoundError on Deadline: 2026-06-30 19:46:49: 0: STDOUT: *** Failed to load 1 files 2026-06-30 19:46:49: 0: STDOUT: - C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\batchdelivery_0.4.3\ayon_batchdelivery\plugins\publish\extract_ocio_config_publishing.py 2026-06-30 19:46:49: 0: STDOUT: ********** 2026-06-30 19:46:49: 0: STDOUT: Traceback (most recent call last): 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\core_1.9.7\ayon_core\pipeline\publish\lib.py", line 403, in publish_plugins_discover 2026-06-30 19:46:49: 0: STDOUT: module = import_filepath( 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\core_1.9.7\ayon_core\lib\python_module_tools.py", line 45, in import_filepath 2026-06-30 19:46:49: 0: STDOUT: module_loader.exec_module(module) 2026-06-30 19:46:49: 0: STDOUT: File "", line 850, in exec_module 2026-06-30 19:46:49: 0: STDOUT: File "", line 228, in callwith_frames_removed 2026-06-30 19:46:49: 0: STDOUT: File "C:\Users\mueller9\AppData\Local\Ynput\AYON\addons\batchdelivery_0.4.3\ayon_batchdelivery\plugins\publish\extract_ocio_config_publishing.py", line 19, in 2026-06-30 19:46:49: 0: STDOUT: import lablib 2026-06-30 19:46:49: 0: STDOUT: ModuleNotFoundError: No module named 'lablib' It looks like lablib is shipped with the addon itself and not part of the dependency package. However, this error does not seem to have a negative effect on the deadline job, in this case a farm publish from nuke. I guess it has something to do with the fact that the sys path is modified on_host_install and therefore not being executed during a headless publish session on deadline. Maybe this can be handled in a nicer way so we avoid the ModuleNotFoundError? Or is this probably causing issues elsewhere?
Sebastian Brandhuber
🐛
Bugs
Merging Project Setting Team and Project Access
Wild thought: Doesnt it make more sense to merge both of these pages together? Both of them define user access rights, one group based and one individual based. What are the benefits of not merging both functionalities on one? I've had producers get lost because they were overlooking Project Access because they went straight for Team, and the other way around, because they were looking for just “Assigned Users” functionality but split over two different pages.
Dieuwer Feldbrugge
1
Production
+1
💡
Feature requests
Merging Project Setting Team and Project Access
Wild thought: Doesnt it make more sense to merge both of these pages together? Both of them define user access rights, one group based and one individual based. What are the benefits of not merging both functionalities on one? I've had producers get lost because they were overlooking Project Access because they went straight for Team, and the other way around, because they were looking for just “Assigned Users” functionality but split over two different pages.
Dieuwer Feldbrugge
1
Production
+1
💡
Feature requests
Bundle creation - default options
When creating new addon bundle, “Archived” is selected by default - that doesn’t make much sense when creating a new bundle. It would be also nice if the launcher would be pre-filled with the latest available.
Ondřej Samohel
🐛
Bugs
Bundle creation - default options
When creating new addon bundle, “Archived” is selected by default - that doesn’t make much sense when creating a new bundle. It would be also nice if the launcher would be pre-filled with the latest available.
Ondřej Samohel
🐛
Bugs
Batchdelivery nuke_template_processing does not run with Nuke14/Py3.9
The script “nuke_template_processor.py” fails with stderr: Traceback (most recent call last): File "C:/Users/brandhuber/AppData/Local/Ynput/AYON/addons/batchdelivery_0.4.2/ayon_batchdelivery/scripts/nuke_template_processor.py", line 229, in def get_upstream_colorspace_data(start_node) -> dict[str, str] | None: TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType' when run with Nuke 14.1v2, because its python version 3.9.10 does not support using the bitwise OR operator (|) for union type hinting. Adding this line from __future__ import annotations on top of the code fixed the problem and the delivery processes as expected.
Sebastian Brandhuber
1
Pipeline
🐛
Bugs
Batchdelivery nuke_template_processing does not run with Nuke14/Py3.9
The script “nuke_template_processor.py” fails with stderr: Traceback (most recent call last): File "C:/Users/brandhuber/AppData/Local/Ynput/AYON/addons/batchdelivery_0.4.2/ayon_batchdelivery/scripts/nuke_template_processor.py", line 229, in def get_upstream_colorspace_data(start_node) -> dict[str, str] | None: TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType' when run with Nuke 14.1v2, because its python version 3.9.10 does not support using the bitwise OR operator (|) for union type hinting. Adding this line from __future__ import annotations on top of the code fixed the problem and the delivery processes as expected.
Sebastian Brandhuber
1
Pipeline
🐛
Bugs