Do I not have a proper configuration environment set up for Episodes, perhaps?
So if you set the context on the collected item at collection time, then it will try to load the publish plugins from the environment yamls that match the context on the item, whilst I think this behaviour makes sense, it does usually catch people out.
This doc explains how the environments work. But basically it sounds like you don’t have an environment yaml file for your episode context containing the relevant engine and publish app settings.
Yeah, so this actually another rough edge. The difference between setting the context on the item during collection, and the user setting it via the context picker is that, as mentioned above if you set it during collection it will search for the plugins in the environment that matches the context. Whereas when you pick it from the context picker, this is after collection time, and so it doesn’t re-evaluate what plugins should be available, so in fact just uses the plugins from the environment that matched the item’s context originally, which by default would be the current engine context.
We have talked about changing this behaviour and do have a ticket logged to do so, but it’s not so straight forward.
Consider this, if you change the context of an item via a plugin, in the plugin’s UI panel, then potentially this new context might point to an environment with different plugins, so the plugins could change each time you pick/change the context on an item. Now if the plugin itself changed the context then it could actually be throwing it’s self away, and even if the plugin did exist in the new environment, we would need to track if it was the same as the previous plugin so we could preserve any settings the user might have entered, but the plugin might actually have different configured settings in this new environment so which would take precedence?