You can see in this rule history that this rule has started to fail. The log reads the reason, which is something I've seen with rules that have actions.





My rule doesn't have any action, only fetches, merges and transforms. It has never been an active rule, and all of these runs are manual. Recently it has started to fail, the stated reason is that the rule is not active. 





I'm not sure why this would have changed, nothing has changed on my end. 





Again, I've seen that message before, but only on rules that have actions. 





I have another rule that I just ran successfully that also doesn't have actions, but does not throw that error. 





Things I can guess, perhaps there's a specific class of objects that can't be included on rule runs that are inactive?





The work-around is to activate the rule, but that seems really silly for a rule that isn't scheduled, only needs test runs and doesn't have any actions.