i’m recently trying to implement Ayon in our studio, so far everything works well, but since a few days any object/entity created on the client/ayon side doesn’t sync to ftrack anymore. what ever is created is not getting a unique ftrackid but the inherited id and path from it’s parent. i reinstalled ftrack addon reconfigured the ash worker and leecher processor and transmitter services matching the addon version. api keys are doubble checked and the sync from ftrack to ayon works well. the event viewer doesn’t show any errors and ftrack.sync states “finished”. comments created in ayon get synced to ftrack. did i just misconfigure anything or is this a known problem around?
update:
I restarted from scratch, setup a new VM, pulled everything from scratch reconfigured everything and the result is the same.
the transmitter logs says:
2025-10-22 08:43:22 INFO Processing event: 2aec883caf2311f0a259a24dd1e6e2ad
2025-10-22 08:43:22 INFO Unhandled action ‘created’
2025-10-22 08:43:22 INFO Processing finished
for every object created in ayon.
i tried different ftrack addon versions reconfigured the services according but it doesn’t change anything.
Is anybody experiencing the same?