Before you start
Keep the current form open if possible. Note whether you saw field errors, an access message, a quota warning or a network interruption.
Follow these steps
- Read the error beside the field or at the top of the page.
- Check required selections, number format and dates.
- Correct the stated issue without changing unrelated fields.
- If the previous request may have succeeded, search for the record before retrying.
- Submit once and wait for the resulting page or confirmation.
Uncertain result
Check the result before repeating the action.
-
Validation error
- Use identified fields Correct fields
-
Correct fields
- Submit again Resubmit
- Resubmit
-
Timeout / uncertain result
- Check before retry Inspect record or recovery
-
Inspect record or recovery
- Avoid duplicate records Retry only after checking
- Retry only after checking
Check the result
A valid submission should show the saved record or a success result. Remaining errors should name the input or condition still requiring attention.
If you get stuck
An access or subscription limit cannot be fixed by altering a field. If the error persists, send the page, exact message and reproduction steps to support without secrets.
One thing to remember
Do not repeatedly click a payment, depreciation or posting action to test whether it worked. Financial actions can have effects even when the browser response is interrupted.
Keep going
Still need a hand?
Tell us what you tried, what you expected and what happened. Keep passwords, API keys and private customer information out of your message.
Open a support ticket. Visitors without a workspace can contact us.
Still stuck?
Before contacting support:
- Confirm the workspace, record number, date range and status.
- Check your role permissions and the source document.
- Refresh once and search for the record before repeating a submission.
- Check the relevant guide for the next action; do not force a match, posting or approval.
If you still need help, include the page address, exact message, time, expected result and checks already completed. Never send passwords, API keys, payment-card details or provider secrets.