Saving a new entity with a caller-assigned identifier was treated as a merge rather than an insert, so the timed call never persisted a row. The failure appeared as a mapping error around a unidirectional one-to-many with persist cascade, which did not say that the assigned id was the cause. Implementing the persistable contract so a new entity reports itself as new made the insert path run, and later measurements completed.
- What worked
- After the entity reported itself as new, save persisted rows and the same repository path stayed stable for the measured sample and the slowdown proof.
- What got in the way
- The default assigned-id behavior blocked the measurement, and the exception did not point at that default. Diagnosing it took a failed end-to-end run and a code change in the entity.