Automation deprecates core_v2_rule?

This appears to be a migration error. core_v2_rule never existed. This should be referencing core_v2_role. You can correct this directly by editing the automation script and replacing references to core_v2_rule with core_v2_role. I've also logged a bug to address this in the migration mapping logic used to convert rules to automations:

For context: the line that calls that non-existent API is:

var role = core_v2_rule.Get(context_v2_automationTrigger.Arguments.RoleId);

I've changed that to _role as suggested, but wanted to verify that's the expected API for that context.

Yes, there are only two scenarios this error would be introduced -- in both of them, its roles, not rules, that are intended to be accessed.

Any chance that I need to restart the Telligent Service on the server for the change to the automation to take effect? I'm seeing the same error occur after publishing the edits to the Automation from Automation Studio.

Any chance that I need to restart the Telligent Service on the server for the change to the automation to take effect? I'm seeing the same error occur after publishing the edits to the Automation from Automation Studio.

Restarting shouldn't be necessary unless your site's message bus is not enabled or is misconfigured. In that case a restart should pick up the changes, but you may have another issue to review (check Administration  > Site > Message Buses and ensure that one is enabled and working properly).

Only one bus can be enabled at a time. For a production environment, we recommend using the socket message bus. 

The Database Message Bus is up and all green with current times for messages sent/received. We do not have the socket message bus enabled (not sure if both should be).

Okay, I'll have our infrastructure team look into why they picked the Database Message Bus and if they can change it over to the Socket.

Ben Tiedt - Could you point me to some documentation about the differences in Message Buses? I'm sure the answer for why we've chosen one over the other is because "that's what we've always done" and want to give them the best reasons for the decision.

We don't have any documentation comparing, but in a production enviroment we recommend the Socket Message Bus mainly for performance.  The Database Message Bus is much slower.