Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
A write to the heap was refused because the clock failed to give a time. Let's see why time matters here. Every version of every field in the heap carries a timestamp, a single canonical nanosecond. And the clock is read in exactly one place, so the question, when was this version written, has exactly one source of truth. History depends on that. Versions are ordered by their stamps, and time travel with asof reads the heap as it was at a given moment. Now, suppose the clock does not answer. The engine could stamp the version with a guess, or with the last known time. But an invented time would slide into the history as a fact, and every later question about order would be built on a false stamp. So rush refuses the write. The first slot names the column that was being written. This is rare, and usually points at the machine rather than at your script: a broken clock source, or a restricted environment. Check the system clock, and then try the write again.
Text from the Rush engine's error catalogue.