Resolve editor and save problems
Keep a local copy of all unsaved workspace content before reloading or clearing browser data.
The application will not load
- Open regex101 in a supported, updated browser.
- Verify that your browser or network does not block page resources.
- Try a separate browser profile with the default configuration.
- Compare the result with browser extensions disabled in that profile.
Content blockers, network filters, or stale cached resources can affect loading. Use the ad-blocker guide to investigate blocked resources.
A workspace will not save
- Copy all unsaved workspace content to local files. Include every test string, replacement value, unit test, and pipeline layer.
- Verify that your network connection works.
- Verify that you are signed in to the expected account.
- Inspect the save error before retrying.
- Try a new workspace with a short synthetic input.
Matching can continue in the browser while a save request fails. A save can fail because of permissions, feature access, payload limits, or an unavailable service. A workspace owned by another account can restrict updates.
If saving succeeds, reopen the resulting link to verify the saved version. If you cannot reopen it, retain the local copy and report the error.
A tool or match does not finish
Use the control for the operation you are running:
| Operation | Control |
|---|---|
| Unit tests | Select Cancel tests. |
| Pipeline | Select Cancel pipeline. |
| Benchmark | Select Cancel benchmark. |
| Matching | Right-click the input tab and select Disable to prevent further matches. |
Disabling an input prevents new matching requests. A match already running can continue until its timeout.
- Reduce the test input.
- Remove optional pattern sections until the delay disappears.
- Compare the engine and flags with your application.
- Re-enable the input when you are ready to match again.
The performance guide shows how to compare the pattern against selected inputs. If a tool is unavailable, check its engine requirements and account permissions.
Browser data appears missing
Private browsing, cleared site data, and a different browser profile can remove or hide local editor state. Unsaved browser state is not a substitute for a saved workspace or local copy. An anonymous permalink does not automatically belong to the account you later use.
Before clearing site data, preserve all unsaved workspace content and anonymous deletion links. Then reopen known saved access links and verify the account used for account-owned work.
Report the error
A report can include the browser version, operating system, flavor, flags, operation, error text, and a short synthetic reproduction. Do not send credentials, private deletion links, or raw customer logs. Network archives can contain authentication headers and input data. Review them before sharing.