ArgumentError: wrong number of arguments (given 0, expected 1) in upcoming_change_stable_opted_out problem check — flooding logs

Thanks for reporting, I think your hunch might be true because it’s happening on a different problem check too:

A scheduled admin dashboard problem check (group_email_credentials) errored. : ArgumentError : wrong number of arguments (given 0, expected 1)

This is a fairly recent change, I’m not sure if this only applies on our hosting, but there is this link in the admin sidebar that shows this information now.