A runbook trigger that has tenants configured but calls an untenanted runbook will still call the runbook per tenant

[ryanrousseau]

Severity

No response

Version

2023.3.12994

Latest Version

None

What happened?

I converted a runbook from tenanted to untenanted (settings say it explicitly cannot be run against a tenant).

I forgot to remove the tenants from the trigger definition and only today noticed that the trigger was running the runbook per tenant.

Reproduction

• Create an untenanted runbook.
• Create a runbook trigger for the runbook.
• Add tenants to the runbook trigger.
• See that the runbook is triggered and executed in the context of each tenant listed.

Error and Stacktrace

No response

More Information

No response

Workaround

No response