Hi there, Can you confirm this bug? If I’ve got a custom engine (eg a fork of tk-houdini), and then I upload that as a toolkit bundle. I then define the engine location as a “shotgun” type descriptor pointing to this uploaded package. It appears that the {engine} token used in hook paths doesn’t w…

Hey Patrick This looks like it’s very similar to this topic? [image] Names for apps/frameworks specified via shotgun descriptors Pipeline Integrations We’re using app and framework descriptors of type “shotgun” to deploy tools remotely as described here: https://develope…

I’ve merged the replies over to the other topic so we can keep the conversation in one place. Cheers Phil

Possible hook path bug

Pipeline Integrations

Topic		Replies	Views
Names for apps/frameworks specified via shotgun descriptors Pipeline Integrations descriptors	15	3032	May 14, 2025
Custom TK engine name error Uncategorized	3	634	November 12, 2021
Hook with a new path Pipeline Integrations	1	1240	December 1, 2019
Possible bug: path value disappearing on hook expression being resolved? Pipeline Integrations engine , fptr-tk	1	223	May 16, 2023
Custom Apps and Creating new Projects Pipeline Integrations	6	1041	November 3, 2020

Possible hook path bug

Related topics