We love your Feedback!

Please tell us how we can make AYON work better for you. You can also report bugs or ask questions if our Help Portal is not helping.

If you’re looking for developer resources, you can find all of them on our Developer Portal

Network connection issues, retries, and user experience

Network timeouts or connectivity issues currently manifest in myriad fashions and during file/publish operations can raise non-user-facing errors and mangled pipeline operations. Rather than selectively creating defensive fallbacks in the arbitrary places where these issues happen in operations, the entire pipeline should create a more global ayon_api solution where we have connection retries with exponential fallbacks, and upon final failure raise a dialog explaining network or connectivity issues and instruct the user to try again in 5-10 minutes, or if this persists check their network connection, or if that does not work, to contact pipeline engineering.

Aleks Berland

💡

Feature requests

Tray Publisher - CSV ingestion

When publishing a csv - which was made as yuou suggest, I’m getting this error. Traceback (most recent call last): File "/home/luciano.cequinel/.local/share/AYON/dependency_packages/ayon_2502101346_linux-rocky9.zip/dependencies/pyblish/plugin.py", line 528, in __explicit_process runner(*args) File "/home/luciano.cequinel/.local/share/AYON/addons/kitsu_1.2.7/ayon_kitsu/plugins/publish/collect_kitsu_entities.py", line 51, in process kitsu_entity = gazu.entity.get_entity(kitsu_id) … File "/home/luciano.cequinel/.local/share/AYON/dependency_packages/ayon_2502101346_linux-rocky9.zip/dependencies/gazu/client.py", line 303, in check_status raise ParameterException(path, text) gazu.exception.ParameterException: ('data/entities/sequence', 'Malformed ID.')

Luciano Cequinel

🐛

Bugs

Feature Request: Pinned Comments & Threaded Replies in Task Activity Feed

Summary: I’d like to propose two enhancements to the comment/activity feed section in AYON’s web task view: Pin Comments — ability to pin one or more important comments to the top of the activity feed (e.g., briefing notes, important decisions, client feedback). Threaded Replies — ability to reply directly to a specific comment in a thread, keeping conversations organized and contextual rather than a flat list. Current Behavior: The activity feed currently shows comments in a flat chronological list. There’s no way to group related replies under a parent comment, or highlight critical comments for visibility. AYON does support Comment Categories for visibility control, but there’s no threading or pinning mechanism. Problem This Solves: In a busy production task with many comments from artists, TDs, supervisors, and clients, it becomes very hard to: Track which reply belongs to which discussion point Keep important notes (like a brief or approval status) visible without scrolling Proposed Solution: Add a “Pin” icon on comments (visible to users with sufficient permissions) that anchors the comment to the top of the feed Add a “Reply” button on each comment that nests responses under it in a collapsible thread, similar to Slack threads or Discord replies Use Case Example: A supervisor pins the shot brief at the top. Artists reply in threads to specific feedback comments. The feed stays clean and everyone knows what’s actionable. Who Benefits: Studios with large teams, review pipelines, and client-facing workflows — especially when combined with the existing Comment Categories feature. I’m happy to discuss further or provide mockups if helpful. Would love to know if this is on the roadmap!

#youssef#

💡

Feature requests