@Tilix4 @Danell any chance one of you know more details since it’s Kitsu related?
A wild guess:
I’m pretty sure the Houdini Review instance will be of family review and maybe it’s not e.g. render or alike and thus doesn’t trigger for the plugins:
- https://github.com/ynput/OpenPype/blob/d81926bb88d46207b6650dd81aac5001015526c1/openpype/modules/kitsu/plugins/publish/integrate_kitsu_note.py#L12
- https://github.com/ynput/OpenPype/blob/d81926bb88d46207b6650dd81aac5001015526c1/openpype/modules/kitsu/plugins/publish/integrate_kitsu_review.py#L11
A quick glance over the code actually shows me that the families are a bit odd for this case anyway. It’s a context plugin that runs if ANY of those families is present, but when that’s the case then it runs over all instances in the context even those that are not of those families the plugin filters to. So as soon as 1 “render” instance exists then all instances are considered for notes integration, etc. (and then it still filters to only those that have the ‘review’ family).
Not sure why the logic is that way, but it almost sounds like this should actually include review in the Plugin.families as well + have the other logic for instance in context: to actually also exclude the ones that do not match. Or better, turn them into InstancePlugin if they just need to run per instance anyway.
Note: I don’t use Kitsu, so I’m not sure of the approach.