Repair and Recovery

When 2Timer itself misbehaves (a white screen, an old version that won’t go away) or a meet’s data looks wrong, use the smallest tool that fixes it. 2Timer’s tools range from fixing the app without touching any meet, through fixing one meet, to deleting everything 2Timer keeps in this browser. Make a .2t backup of any meet you can still open before you use a tool that deletes data.

Which recovery tool to use

From least to most drastic:

1. App update: an old version or a stale screen. Check for Update in Diagnostics.
2. Repair App: a white screen, or 2Timer won’t load properly in any meet. Meets, settings, and saved keys are kept.
3. Data Issues in a meet: duplicate bibs, entries not linked to an athlete, and other identity problems, each with its fix.
4. Clear or purge one meet’s data: wrong results, a test run to wipe, or a whole category to remove. See Purging Results and Resetting State.
5. Delete one meet: from the Meets screen.
6. Delete a database or clear a table in Diagnostics: only when you know exactly what it holds.
7. Delete All Local Data: every meet and setting in this browser, gone.

Open Diagnostics (/repair)

Diagnostics is the small Diagnostics link at the bottom of the sidebar, next to the version, on the Meets screen, Settings, and other screens outside a meet. It isn’t shown inside a meet. You can always type the address: manager.2timer.app/repair. That works even when the Meets screen won’t load.

The page has three panels: App Updates, Storage Diagnostics, and Repair Tool.

Check for an app update

In Diagnostics, App Updates shows the version and build you’re running.

1. Press Check for Update.
2. “You are on the latest app version available to this browser” means you’re up to date. “New version available” adds Update Now: press it to load the new version.

Checking needs the internet. 2Timer also checks by itself every 10 minutes and offers Update Now in a box at the bottom right. See Offline Access and PWA.

White screen or an old version stuck after an update

If 2Timer shows a white screen or a broken page after an update, or keeps loading an old version:

1. Open manager.2timer.app/repair.
2. Try Check for Update first.
3. If that doesn’t fix it, press Repair App under Repair Tool.

Repair App needs the internet: it removes 2Timer’s offline copy and reloads it fresh. Don’t run it at a venue with no internet unless 2Timer is already unusable.

Repair App: what it clears and what it keeps

Repair App (“Repairing the app. Your meets, settings, and saved system keys and sign-ins are kept…”) clears 2Timer’s offline copy of itself and the choices it remembers on screens, then reloads.

It keeps:

• every meet, with all its data;
• your settings: your systems, preferences, and company details;
• the keys and sign-ins saved for your systems;
• this device’s place as your live results publisher, so the next send doesn’t ask to take over;
• your 2Timer sign-in.

It clears:

• 2Timer’s offline copy, so the reload needs the internet;
• saved spreadsheet column maps;
• remembered filters and choices, such as the Seeding queue’s filters, the event chosen on Entries, and the new-meet wizard’s last genre and venue;
• the install card’s Not now (the card comes back).

A system asks for its key again after a repair

Repair App keeps your saved keys and sign-ins. Older versions of 2Timer didn’t: after a repair with one, the keys and sign-ins saved for your systems on this device can’t be read. If a system asks for its key again, open Settings → Systems and save them again before the next race: ONETIME and Total Active Sports keys (Save key), Sign in to RunSignUp again, and Save the RaceRoster, S3 / R2, and FTP details. Then use each row’s test (Test key, Test sign-in, Test the bucket, Test the server). RunSignUp can still look signed in until you test it.

After such a repair, a live results destination may ask Take over publishing from the other device? on its next send, because the browser counts as a new publisher. Choose Take over publishing.

This meet file needs repair

When the meet’s dashboard says This meet file needs repair., press Download a backup, then Download .2t File, to save a .2t backup of the meet. Then, on the home screen, choose From .2T File and open that backup, which rebuilds the meet as a fresh file. See Importing a 2Timer Backup.

Data Issues: duplicate bibs and other meet problems

Data Issues lists the problems in one meet’s athletes and entries, each with its fix: duplicate athlete bibs, athletes missing bibs, entries not linked to an athlete, duplicate linked entries, athlete data conflicts, roster and import warnings, Lynx results needing review, and blank entries.

It isn’t in the sidebar. Reach it from:

• the dashboard’s N data issues need your review. row, with Review data issues;
• Open all data issues on a held read.

“No data issues found for the current meet data” means the meet is clean. See Athletes and Entries for the bib fixes.

Delete one meet

1. On the Meets screen, open the meet’s ⋮ menu.
2. Choose Export .2T backup first if you might want it back.
3. Choose Delete.
4. Delete meet lists what goes: details and settings, events, divisions, waves, athletes, teams, results, reads, connections, and markers. There is no way to recover a deleted meet.
5. Type the meet’s name exactly (with its start date, if another meet has the same name) and press Delete meet permanently.

Remove some data from one meet

To wipe results after a test run, clear one race’s times, clear bibs, or remove whole categories such as reads or entries, use the meet’s own tools: Entries → Tools → Clear Data…, Athletes → Tools → Clear Bib Numbers…, or the dashboard’s Remove data… → Purge results… or Purge meet data…. See Purging Results and Resetting State.

Storage Diagnostics: what 2Timer is storing

Storage Diagnostics in Diagnostics shows everything 2Timer keeps in this browser, across all meets:

• Origin storage: space used and available;
• IndexedDB databases: how many meet, settings, test, and other databases;
• Service workers and Cache Storage: 2Timer’s offline copy;
• Web storage keys: remembered settings;
• the IndexedDB inventory: each database with its tables, record counts, and size.

Refresh Diagnostics in Repair Tool reads them again.

Delete one database or clear one table (advanced)

In the IndexedDB inventory:

• Delete on a database removes it from this browser. Deleting a meet’s database also removes the meet from the Meets list. Type DELETE to confirm.
• The 🗑 button on a table clears every row in that table. Type DELETE to confirm.

These skip all of 2Timer’s checks. Clearing one table can leave a meet inconsistent, so use them only when you know exactly what you’re removing. To delete a meet, the Meets screen’s Delete is safer.

Delete All Local Data

Delete All Local Data, under Repair Tool, permanently deletes everything 2Timer keeps in this browser profile on this device: every meet, your settings and systems with their keys, the account details 2Timer remembers, and 2Timer’s offline copy. Type DELETE ALL to confirm. 2Timer then reloads empty, which needs the internet.

Use it only when you mean to start from nothing. Back up every meet you want first.

Typed confirmations

The tools that delete data ask you to type a word first:

Recovery checklist

• You chose the smallest tool that fixes the problem.
• You made a .2t backup first, when the meet could still be opened.
• After Repair App, each system in Settings → Systems passes its test.
• After a repair or deletion, 2Timer reloads cleanly and the meets you meant to keep are there.

Related Pages

• Purging Results and Resetting State
• Importing a 2Timer Backup
• Offline Access and PWA
• Systems and Connections
• Athletes and Entries

Metadata

• Last Updated: 2026-10-13
• Document Version: 0.2
• Status: Active