Does this mean you get the same result adding a task to it or that an already existing task in the plugin has this behaviour?
Thanks for the information! It feels a little hacky to have to clear it but it’s certainly a useful workaround.
I’ll mark your post as the solution for others’ convenience. Hopefully the broader cause can still be identified, I guess the question becoming: why are tasks registered twice in some plugins and not others?