-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Labels
type: bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues and added correct labels.
Description
Current Behavior
Rendering locall work but rendering on farm doesn't.
I tried figuring out the problem so here are what I've found so far:
- Typically, the
ayonUsdResolverplugin is added on run time. However, the hook responsible for that doesn't run on farm causing the resolver to not be present, see here - once the hook works, the resolver logs
after some debugging, it turns out it fails to login becasue the expected value of
2025-08-07 19:03:00: 0: STDOUT: [2025-08-07 19:03:00.610] [warning] not logged in 401AYON_API_KEYis not the AYON API, but rather it's a bearer token. we get one when we login to the server. this is mentioned in my example about testing the AYON CPP API in 360 fix outdated example of cpp api ayon-documentation#382 . yes, this is not related to the resolver itself, it's related to the AYON cpp api. - about pinning
- When this logic in extract pinning runs in Houdini, it always exports the pinning file to a temp location which is deleted shortly after submitting the DL jobs. which I assume is wrong as the DL jobs expects to access that file.
PINNING_FILE_PATHI don't see this environment variable set on the submitted DL Job.- The
UsdPinningRoothook has a bug here where it should beroots = anatomy.roots
I'll keep updating this list.
Steps To Reproduce:
you can reproduce it by publishing a render while loading a product that uses entity URI. e.g., in Houdini

Additional context:
Version
Version of the server, ayon-core and the addon that's affected
What platform were you running when you found the bug?
Windows
Linux - Rocky9
Linux - Ubuntu
MacOS
You can also provide any additional information relevant to the issue.
Relevant log output:
Metadata
Metadata
Assignees
Labels
type: bugSomething isn't workingSomething isn't working