Why can't I…

Crown blocks things on purpose. Almost every block is a control doing its job, and the message on screen names what's missing — but if you're mid-run and want the short version, this page is organised by what you were trying to do.

…record a production step

"Blocked by a start gate." The step needs a condition met first:

• Calibration not current — record a calibration for the equipment bound to the step. If the message says no equipment is bound, the step or its stage needs equipment on it before the gate can be checked at all.
• Sanitation not recorded today — log today's sanitation under Documents → Sanitation.
• Allergen changeover not recorded today — record the changeover under Documents → Allergen control.

An adjusted result clears a gate the same as a pass. See Recording production steps.

The Record button is greyed out on an ingredient step. You have to select the lot you used first — that link is what makes the finished product traceable. See Assigning lots to a batch.

A quick batch won't complete. Same start gates apply, and you can't clear them from the quick-batch form. Record the underlying check, then complete.

…use a lot

It's on hold. A held lot shows an On hold badge with the reason, and can't be consumed until you clear the hold from the lot drawer. That's the point of a hold. See Managing inventory and holds.

It isn't in the picker. Check the quantity on hand — a lot that's been fully consumed won't offer itself.

…edit a recipe

The fields are read-only. Editing is draft-only. An approved version is locked apart from its description and notes, which is exactly what makes a batch record trustworthy: the recipe a batch ran against can never change after the fact. Use Edit as new version. See Managing recipe versions.

A stage shows an amber drift badge. Not a block — the stage template it was imported from has been edited since. Update the stage or ignore it. See Reusing stages with templates.

…release a batch

Every CCP needs a reading. A critical control point with no reading, and no deviation explaining why, blocks completion.

A lab test is still open. Finalize it as passed, passed with deviation, or failed.

Passing without a certificate of analysis needs a reason of at least 20 characters. Write what you're relying on instead — the lab's emailed summary, an in-house result. See Lab testing a batch.

The button doesn't say what the article says. At internal QC the actions are Send to lab and Release (no lab); at pending lab they're Release batch, Release with deviation and Reject batch. See Releasing a batch.

…correct something already recorded

Most records can be corrected, with a reason that stays on the audit trail:

Two things Crown won't do: backfill a reading that was never captured, and let you clear or move a CCP reading out of spec without a deviation.

A mis-recorded bundle pack is voided rather than amended — its components return to stock. See Bundles and assembled packs.

…save a receipt

The inspection needs a description. Both Fail and Accept with damage require you to describe the issue before saving.

The damaged amount is rejected. It can't exceed the quantity received.

Accept with damage has nowhere to put the numbers. Enter your line items first, then record the damaged amounts against them.

…find a page

A whole section is missing from the menu. Admin-only areas — Users, Billing, Company, Lot Code Format, Import, Data — are visible only to members with the Admin role. See Inviting your team.

Nothing saves, and everything reads fine. Either you're on a Viewer account, which is read-only by design, or the workspace is in read-only mode after a cancelled plan. See Billing and subscription.

You were signed out. Sessions end after 30 minutes of inactivity. See Your account and signing in.

Still stuck?

If the block doesn't match anything here, the message on screen is the best guide — Crown names the specific condition rather than failing generically. Use the in-app feedback button if something blocks you with no way forward.