Thank you for all your responses. We discovered, with Intersystems help, there is a bug in our current version of Cache 2018.1.7. We found a workaround by excluding the NOW hour.