Clarify CronJob behavior

In the docs I read this:

For every CronJob, the CronJob Controller checks how many schedules it missed in the duration from its last scheduled time until now. If there are more than 100 missed schedules, then it does not start the job and logs the error

So a CronJob may get stuck forever?

Or it simply skips the past events but executes the future events normally?