Yes and it’s due to a change that happened in our pool api and the fix was released in testing channel just recently (shortly after the change that cause it):
The issue was diagnosed by forum member @kbogert in the following forum thread:
with an initial report and assistance from @KarstenV; and core code contributor @Flyer.
You will need to re-create that scheduled scrub job as then it will contain the new style pool api info.