# Repeated "New timer generated is less than read level" in Temporal history logs

## The problem

After adding a second node to a freshly bootstrapped one-node Temporal cluster, the history service logs "New timer generated is less than read level" once per second, indefinitely, on the original node. The cluster otherwise works. Temporal 0.23.1 on Amazon Linux with Docker.

## The verified fix

Per a maintainer, this warning is benign: it is a protection that keeps the server from generating timers below the read level (which would skip timers), not a sign of a broken cluster. In the reporter's case it was triggered by setting a workflow execution timeout on a cron workflow; removing the execution timeout stopped the messages. The team later converted it to a metric and lowered the log level to reduce confusion.

Source: https://github.com/temporalio/temporal/issues/425