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 rejected by tungsten, the part of the engine that keeps the heap honest. Here is how that works. Every write, whether it is a new version of a field, a draft being poured, an inner collection, or a final commit, passes through tungsten, and tungsten judges the whole thing. Is the being alive? Does the write follow the rules of the C axis? Is the timestamp later than the last one? Does it respect the law of the holder? If any answer is no, the write simply did not happen. And the door does not pretend. It reports tungsten's own words, so nothing is hidden or paraphrased. The first slot names what was being written: a column, the answer's draft, or the seal. The second slot is tungsten's verdict. Imagine writing to something that was already retired, the verdict will say so. Use the verdict to find the cause: a being that is gone, a stale version, or a rule that was broken. If the cause is not in your script, report the message as it is.
Text from the Rush engine's error catalogue.