Troubleshooting test saves

If you’re trying to save changes to your browser or mobile test in the mabl Trainer and something isn’t working, use this article to troubleshoot.

“Save Conflict” warning

The Save Conflict warning appears when your save would overwrite a newer version that another user has saved on the same branch.

mabl shows this warning in two situations:

• Test version conflict - a new version of the test was saved after you launched the Trainer and before you saved your own changes.
• Flow version conflict - A shared flow in the test was updated from another test after you opened the Trainer and before you saved your own changes. Even if your changes didn’t touch the flow, saving your changes will elicit the save conflict modal.

In both cases, the updated version was saved to the same branch.

There are two ways to resolve save conflicts:

• Save my changes, then Confirm - overwrite the other user’s version with yours. Their saved work becomes the previous version, and your version becomes the latest.
• Cancel - close the warning and return to the Trainer with your changes still in place. To preserve your work, create a new branch in the Trainer and save your changes to that branch. You can merge your changes later using conflict resolution.

“Error saving test. Try again or contact support.”

This message indicates the Trainer couldn’t reach the mabl servers to save your test, which can happen if there is a network interruption, token expiration, or temporary server problem. Try the following steps to resolve:

1. Click Save again to rule out temporary connection issues.
2. Check your network connection. Try loading app.mabl.com in a browser, toggle your VPN if you’re using one, or switch networks if you can.
3. If saving still fails, contact support. Include what you tried and any error details that appeared.

“Unable to save test: test or flow is too large. Contact support for more information.”

Tests and flows can occasionally become too large to save. If you get this error, try splitting the test into smaller flows or breaking up a long run of test steps with a reusable flow. If saving still fails, contact support and share your details.

Save button doesn’t work

If the Save button is disabled, hover over it to see a tooltip explaining why. For example, if your test has a flow with no steps, the tooltip on the Save button says “Flows can’t be empty.” Follow the action the tooltip describes to enable the save button.

If clicking Save doesn’t save your test and no error message appears, one of your test steps has an error. Look for a red exclamation-mark icon next to one of your steps. Hover over the icon to see a tooltip describing the problem. For example, if your test has a conditional block missing its END step, the IF step shows a red exclamation mark with the tooltip “Conditional statement has no END step.” Resolve the step error described in the tooltip, then save your test again.