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#

1

Production

💡

Feature requests

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

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

🐛

Bugs

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

If I set the task to end on one day using the task tiles (on the right side of the scheduler view), it sets the task end date (on the left side of the scheduler view) to the next day instead of the same day, it is pretty confusing. Is it possible to do something about it?

Jakub Bijak

Production

+1

🐛

Bugs

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

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

Production

+1

💡

Feature requests

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

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

Hi, The batchdelivery addon 0.4.1 is failing during the process in the plugin “collect_offloaded_processing_context” around line 552: "sourceParentFolderName": folder_path.split("/")[-2], This line will fail when folder_path points directly to a folder in the project root, because after the earlier stripping logic there is no remaining / in the path. In our current project structure, shots are located directly under the project root and do not have any parent folders. As a result, this code path will be triggered and the logic will break for those shots. Changing the value to folder_path.split("/")[-2] if folder_path.count("/") > 0 else ““ works as expected and the rest of the process continues without error. Since I don't have access to post this issue directly in the addon's private repository or submit a pull request, I'm happy to track and discuss the status of the bug here. Thanks!

Sebastian Brandhuber

1

Pipeline

🐛

Bugs

Being able to hook parts for one addon to other views/pages on frontend would be very useful. Adding custom widgets/buttons to predefined places could be enough.

Ondřej Samohel

💡

Feature requests

For checking more technical issues or switching between technical data encoded in RGB (like wireframe, ulit texture, color masks) it would be great to be able to switch between individual channels and full composite view in similar fashion as is in other players. Having small buttons next to the Brightness control for example with associated keyboad shortcuts.

Ondřej Samohel

💡

Feature requests

It would be great to wrap parts of the settings into their own individual “modules” that would have UI more suited for the specific task. As example: Color management settings are very cumbersome - you need to set many things on many places, sometimes write exact strings (color spaces names), etc. Having dedicated UI that would ease the pain (along with presets, etc.) would help a lot. Having this modular and customizable, it would open up a way for building much more easier layer on top of low-level settings.

Ondřej Samohel

💡

Feature requests

Currently I’m looking to input events in line with the tasks that are set out amongst the hierarchy however it keeps snapping to the task above when I want it to align with the task - why is this the case - anyone have any suggestions to fix this?

Oscar Robinson

Production

💡

Feature requests

I want to be able to automatically unassign other artists from a task when one artist starts working on it, to prevent duplicate work.

Valentin

1

💡

Feature requests

Currently we often get clients asking what they should do with the sync popup when we’re just sharing a review playlist for them to look at in their own time, this confuses them. I would suggest all review playlists do NOT have syncing on by default, unless some one on the top right clicks START SYNC, which then will notify people if there’s a sync active or not when they open the playlist. This would mean we can just share playlists to people and they’ll be able to find their way more intuitively without thinking there’s some one presenting which they do not know about.

Dieuwer Feldbrugge

3

Production

+1

💡

Feature requests

Often when dealing with clients they might want to have random people rally around a review session. Being able to have single link from which Guests can join ( probably password protected ) without having to fill in every viewers email would be very helpful.

Dieuwer Feldbrugge

Production

+1

💡

Feature requests

I take the latest eMail for the review-tool updates as opportunity to show my pet peeve, as it illustrates it quite well The frame-counter in the bottom left should account for the actual frame numbers. I am aware that mp4 don't save the frame number, but Ayon has all the data already in the system; there's usually no reviewable that doesn't root from a sequence. You don't even need to do some guess-work; if the source sequence starts at 1001, so should the viewer. In the screenshot it “works” because there’s burn-ins, sometimes they are hard to read or not rendered. If there’s really a case where there’s no sequence as base of a reviewable, you could do some guess work. e.g., if Ayon has 1001-1100 inside, and 10 frames handles front/tail, an mp4 with 100f length, it will likely be starting on 1001; if it’s 120f, 991. Or leave it as-is when there’s no data available. The data being available but showing generic ranges seems like a wasted opportunity for the great review overhaul we are receiving :)

LucMeister

Production

+1

💡

Feature requests

EXR seq → MOV in batchdelivery 0.4.1, three bugs in extract_offloaded_transcode.py (transcoder backend, not template): Line 285-286 adds #### to the Write node file regardless of output extension. nuke_template_processor.py around in line 319-325 already has the right VIDEO_EXTENSIONS check (it's already imported at the top). nuke_transcoder.py doesn't set job["output_extension"] like nuke_template_processor.py in line 338 does, so the downstream representation collapse at lines 921-966 never runs for the transcoder backend. Result: ext=mov but files keeps the 34 EXR names → IntegrateDeliveryProduct FileNotFoundError trying to copy nonexistent EXRs. After setting output_extension, the collapse at lines 947-950 calls clique.assemble without checking length. A single-file list raises IndexError. We used a len(files) > 1 guard. We tested and patched locally and EXR seq → ProRes 4444 XQ now lands as a single MOV in publish. Lines 282-291, replacing the original if file_type and (is_sequence or is_video): block: is_video_output = ( bool(file_type) and f".{file_type}" in VIDEO_EXTENSIONS ) if file_type and (is_sequence or is_video) and not is_video_output: write_node_file_name = ( f"{file_head}{'#' * padding}.{file_type}" ) elif is_video_output: write_node_file_name = f"{file_head.rstrip('.')}.{file_type}" if "#" in write_node_file_name: new_repre_files = convert_hashed_filename( write_node_file_name, frame_start, frame_end) Added just before self.log.info(f"Nuke job data: ...") near the end of _prepare_job_data: if is_video_output: job_data["output_extension"] = f".{file_type}" new_repre_files = [write_node_file_name] Line ~947, adding len(files) > 1 to the downstream collapse condition: if ( isinstance(files, list) and len(files) > 1 and output_extension in VIDEO_EXTENSIONS ):

Matti Kaihola

1

Pipeline

+1

🐛

Bugs

Currently when a user is created a `entity.user.created` event is generated, however when the user is modified it does not generate an event, simply logs a message that the user has been changed. Getting like a real event that can be enrolled on would be handy.

sjt-rvx

Production

+1

💡

Feature requests