This should be fixed in the latest version of the discourse-automation plugin.
Thanks again for the report @aas
