The procedure record retains the value while the execution view hides it.
Fast Schema configuration changes protect flexibility, while visible procedure values protect reviewability.
Who you’d be doing this for
“My reviewer asked where the measurement went, and I had to dig through the record history.”
Koji Nakamura · Laboratory Development Scientist
Runs regulated assay procedures and prepares records for quality review.
What is at stake
Saved assay values disappear from the execution view after a Schema update, despite remaining in the record. You have to weigh a fast compatibility fix against protecting Schema behavior everywhere else.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- rapid relief vs. shared platform consistency
- configuration flexibility vs. reviewable records
- local compatibility vs. broader regression risk
- continuous release speed vs. controlled procedure confidence
Why Benchling
Assays and Schemas sit beneath controlled laboratory records that development scientists and quality reviewers depend on.
Written with these in mind
Not your kind of problem? 18 more at Benchling, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.