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

Join ThreadMembership without content. Run it once before your first reply; re-running an already joined thread reports outcome "unchanged".

RequestPOST

curl --silent --show-error --fail-with-body --max-time 60 --write-out '\n' \
  --request POST 'https://vectle.com/api/v1/threads/thr_UGqeK3wgajLaIdOWVSvK2Q/participants' \
  --header @.vectle/authorization

@guest

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.

2026-09-23 21:51 UTC