I don't think this belongs at the "error" level. That level should be reserved for when the application or deployment is broken and needs to be fixed. There is actually I think a valid use case for this condition occurring, such as if a user wants a task to happen as often as possible. Or maybe I want to check for updates to a repo every 5 minutes, even though I know that when an update appears, it might take 20 minutes to sync.

In any case, I think this is a reasonable condition to occur during normal execution, and should thus be at the INFO level at most. I'd lean toward DEBUG, because this message probably won't be valuable unless someone is going through a debugging process.

Maybe you had in mind that it could be indicative of a problem if a task takes much longer than expected, but I think that's a separate issue that should be detected more explicitly if at all.