run: when we determine a timer cannot elapse anymore, really just warn, nothing else

run: when we determine a timer cannot elapse anymore, really just warn, nothing else

When we determine that a calendar expression cannot elapse anymore,
print a warning but proceed regardless like we normally would.

Quite possibly a remote system has a different understanding of time
(timezone, system clock) than we have, hence we really shouldn't change
behaviour here client side, but log at best, and then leave the decision
what to do to the server side.

Follow-up for #12299