Resolve saving and validation problems
Read the validation message, correct the relevant field and verify the saved record before trying again.
Checked on 29 October 2026
Overview
Read the validation message, correct the relevant field and verify the saved record before trying again.
Get to know the screen
Practice example: all names, records and amounts are fictional. Options vary with your school’s curriculum, currency and access.
Phone example
Interface labels are shown in English. Follow the translated steps below to find each control. Follow the sequence, review the recorded information and choose the next step.
Who can use this feature
Use your own account and check the school before opening records. Account checks do not grant a school role. Ask an authorised school administrator to review missing membership, class assignments or feature access; families use their own approved learner links.
Before you start
Have permission to edit the selected record. Keep a copy of unsaved text and note the intended school, year and action.
Required and optional fields
Follow the requirements of the form you are using. The diagnostic details below help you check the problem; they are not a separate form or a request to change your account.
| Field | Requirement | Format or example | Prerequisite |
|---|---|---|---|
| Error and request state | Required when applicable | Keep the exact error, action, page and time. Preserve unsaved text and check whether the original record was saved before retrying. A loading indicator is not a confirmation. | Current account, selected school/year, saved setup records and the actual form’s requirements. |
Picklist prerequisites
Validation belongs to the specific form. Required fields may depend on earlier selections; changing a class or curriculum can clear dependent choices. A missing option must be fixed upstream.
Desktop walkthrough
Check the current screen and the relevant context.
Screen walkthrough · 0:45Download GIF ↓- Check required fields and format before submitting. An unavailable Save button can mean the form is incomplete or a request is already running.
- Use the actual field error or response to identify the correction. In the class resource example, Name is required; an optional description does not replace it.
- Correct the relevant field, review dependent selections and attachments, then submit once. Wait for the success message or a clear error.
- If the request times out or the connection changes, reopen the same list or record and check whether the action was saved before submitting again.
- If correction does not resolve it, keep the error wording and describe the steps to support. Include time and record reference where appropriate, without passwords or private learner details.
Mobile walkthrough
On a phone, scroll above and below the current field for validation messages. Return from the keyboard to review the save control. The example shows an incomplete resource, typing a name and the saved card.
Check the current screen and the relevant context.
Screen walkthrough · 0:45Download GIF ↓Save and verify
Check the saved value in the reopened record, not only the success toast. A button click, loading spinner or navigation away is not proof that the save completed.
Troubleshooting
The form still fails or a duplicate appears?
Stop repeated submissions. Check required fields, permissions, selected year and the saved list. Ask the responsible team to review duplicates; do not delete records while uncertain which action completed.
Before retrying a save or send, reopen the same record and check whether it was already saved or queued. Keep the original wording and error. Repeated clicks can create duplicate actions.
