From Calibration work, choose Resume a group calibration session and open the saved session. Check its title, performed date, procedure revision and actual site before entering more evidence. Saved work belongs to the session and each device's event; unsaved entries still need a successful save.
A device is missing or a new group cannot start
Check the selected organisation, search filters and exact procedure revision. Every selected equipment/requirement pair must use the same approved revision with Allow group execution enabled. Similar titles or different revisions of the same procedure are not interchangeable. Follow Prepare a procedure for group calibration when the method needs configuration or approval.
Use Check group eligibility after changing the proposal. Resolve the reasons shown for the actual date, site, authority, requirements or active work. A saved reservation does not establish fitness to perform the work. If starting new sessions is disabled, ask your administrator about availability; existing group evidence remains readable. Do not recreate equipment or change the method to bypass a blocker.
A reading failed to save
- Keep the page open and check the asset, serial, calibration point and row state.
- Complete the indication, observation time and any required acceptance limits.
- Resolve the displayed error, then use Retry this device for that row.
- Wait for its saved confirmation before leaving or switching views.
Other successfully saved rows remain saved. Blank input means missing evidence, not zero. Edits entered while a row is saving are queued for a subsequent save; check the final state rather than assuming the first response includes them. Use Refresh device filter when you want the displayed roster to reflect newly saved states. A device remaining in a filtered view does not itself mean its save failed.
Another operator changed the same evidence
For an individual reading, use Compare saved value. Compare the current indication, time, limits and shared reference with your retained entry. Use Reapply my entry after comparison only when the entry is still correct.
For a shared response, use Compare latest saved shared evidence, then review the saved revision alongside your retained form. Use Reapply my shared entry after comparison only after that review. Reapplying does not bypass the current version, authority or evidence checks.
For a pre-start roster conflict, compare the latest roster and explicitly reapply the intended list. Once execution begins, the roster freezes. Late devices need another session. Withdraw a device with an accurate reason when it no longer participates; its earlier evidence remains retained.
The next shared point or a device submission is blocked
Open Device evidence readiness and follow that device's individual procedure, results, reference, uncertainty, conformity and review links. Viewing another point does not complete earlier required work. Finish the prerequisites or record an authorised disposition supported by the method. A failed captured outcome does not become a pass, and missing evidence remains missing.
Review the ready devices explicitly before submitting. One incomplete or failed save need not prevent other ready devices from proceeding, but each selected device still has to pass the normal submission checks. Submitting is separate from independent approval or release for use.
Submission was interrupted or only some devices succeeded
Some device submissions may already have committed even if the response was lost. Keep the session open and use Reconcile previous submission. It reuses the original reviewed operation and signature choices instead of submitting successful devices twice. Inspect every persisted outcome and the device's saved status.
On returning to the session, compare the saved outcomes before starting further work. If the recovery action is unavailable, retain the group reference and ask an authorised manager to check the individual saved events. Do not create a replacement group or new events simply because a response was missing. Once the earlier operation is resolved, correct any remaining device blockers and review a new selection for subsequent submission.
A shared correction has not updated a device
Open Shared correction impacts and compare the exact previous and corrected revisions. An eligible editable device must explicitly adopt the latest correction and revalidate its own evidence. A newer correction cannot be resolved by adopting an older pending impact.
Submitted and approved events retain their frozen shared revision. Use their normal controlled amendment or supersession process for an accepted correction; editing the group does not silently change approved results, due dates or issued certificates. See Review procedure execution.
Preserve unfinished entries and report a repeated problem
Choose Stay and save or Cancel if sign-out warns about unfinished entries. Confirming discard erases unsaved local entries; saved server evidence remains subject to normal access. These group forms have no local draft restore and do not support offline work. See Save edits and sign out safely.
For a repeated problem, record the organisation, group reference, affected asset, point or step, displayed message and approximate time. Include an error reference if shown. Share those details with your authorised manager or service operator; omit credentials, signatures, certificate contents and private readings from ordinary support messages.