Publishing

Publishing sends a read-only snapshot of the tournament to the public service. Each publication is a separate upload of the current local data, not continuous synchronization between the desktop app and the public page.

Understand publication and tournament status

The tournament status beside its name is a manual informational label. Selecting Published does not send data, enable synchronization, or confirm that a public page contains the current tournament. Use Publish on Tournament → Overview or Tournament → Match day to perform an actual publication.

Each publication builds a new complete snapshot. After the service accepts it, that snapshot replaces the public representation for the same tournament. Later local edits remain local until another manual or automatic publication succeeds.

The desktop tournament remains the working copy. Publication does not make the public page editable and does not import changes from it.

Understand what the snapshot contains

The snapshot contains the current values of:

the tournament identifier, name, dates, manual status, venue details, organizer contacts, and tournament-points rules;
configured courts;
events in their current order, including category, entries, seeds, final places, and Partner Wanted records;
draws, their assigned entries, round-robin standings, and playoff structure and source positions;
matches, including sides, winner, set scores, status, scheduled time, assigned court, and draw or playoff links;
players whose tournament registration is Accepted, including player name, club, gender, and saved event points.

Only registrations with the Accepted status are included in the snapshot’s player list. Pending and Rejected registrations are not included there. Event entries are collected separately from current event data, so review both registration statuses and entries before publishing.

The snapshot records the time at which it was built. It does not include every piece of local operational state. For example, Match day queue order, player availability controls, and actual start and finish times are not included.

This list describes data sent by the desktop app. It does not guarantee how every field is displayed by the public site.

Configure the Publish token

Obtain a publish token from the site administrator. The token authorizes this installation of the app to send tournament snapshots.

Open Settings from the main navigation.
Enter the token in Publish token.
Leave the field to save it.

Leading and trailing spaces are removed when the token is saved. The field is masked, and the saved value is reused for later publications from this app installation.

An empty token disables Publish on Overview and Match day and disables Auto on Match day. A non-empty but incorrect token enables the controls, but the service rejects the publication as an invalid token. Return to Settings, replace the value, and leave the field again to save it.

Use the public link

Open Tournament → Overview to find the public link beside the globe icon. Select the copy icon to copy it, or open the link in a browser.

The link is formed from the public-site address and the tournament identifier. The identifier does not change when you publish again, so repeated publications use the same link. The presence of a link in Overview does not prove that a first publication has succeeded or that the public page contains the latest local data.

Publish for the first time from Overview

Open Tournament → Overview.
Review the tournament information and the publication checklist below.
Select Publish.
Wait for Publishing… to finish.

On success, Overview shows Published followed by the successful publication time returned by the service. This time is shown for the current open panel; reopening Overview does not load a publication history.

A successful publication from Overview updates the public snapshot, but it does not establish the local Match day comparison baseline. If you plan to use Auto, make one successful manual publication from Match day as described below.

Publish an update from Overview

After changing local tournament data, return to Tournament → Overview and select Publish again. The app builds a complete new snapshot rather than sending only the changes. A successful upload replaces the public representation for this tournament while keeping the same public link.

Use a manual update when changes are outside the Match day badge, such as edits to tournament details, registrations, entries, draws, standings, final places, points, courts, or scheduled times.

Publish manually from Match day

The publication controls above the queue on Tournament → Match day send the same complete tournament snapshot as Overview.

Open Tournament → Match day.
Select Publish.
Wait for Publishing… to finish.

After a successful Match day publication, the app stores a local comparison baseline for this tournament and displays the successful publication time. The +N badge clears because the current match records now match that baseline.

The displayed time is the last successful Match day publication known to this device. It comes from the service response saved with the local baseline. It confirms that this app received a success response at that time, but it is not a live check of the public page. Another device can have a different baseline and displayed time.

Interpret the Match day `+N` badge

After a successful Match day publication, +N counts match records that differ from the local baseline. One match contributes one change when it is new, was deleted, or has a different:

status;
first or second side;
winner;
set score.

The badge does not increase for a court or scheduled-time change by itself. It also does not track changes to tournament details, registrations, entries, draws, standings, final places, points, player availability, or Match day queue order.

The badge is an automatic-publication trigger, not a complete comparison of the local tournament with the uploaded snapshot. When any tracked match change triggers a publication, the full current snapshot is still sent, including other snapshot data that changed. Changes that never affect the badge require a manual publication.

The baseline is stored locally for this tournament on the current device. It is not shared with another device and is not confirmation of what the public page currently displays. Clearing local app data or using another device can remove or change the available baseline without changing the public page.

Before the first successful manual publication from Match day on this device, no baseline or unpublished-change count is available. A successful Overview publication does not create this baseline.

Use Auto in Match day

Auto can publish detected match changes while Match day is open. It runs only when all of these conditions are true:

a publish token is saved;
Auto is selected;
a successful Match day publication baseline exists on this device;
the +N comparison detects at least one change;
no publication is already running.

Auto never performs the initial publication when the baseline is missing. Select Publish manually in Match day first.

Automatic attempts occur at most once per minute. The minimum one-minute interval is measured from the later of the last successful publication time and the latest automatic attempt. After a timeout, network error, invalid-token response, or server error, the baseline is not replaced, the changes remain pending, and another automatic attempt waits until the interval has elapsed. There is no visible retry countdown.

You can correct the problem and select Publish manually without waiting for the automatic interval. Switching to another tournament turns Auto off. Closing Match day stops automatic attempts until the screen is open again.

Publish with an unstable connection

Tournament work remains local when the internet connection is unavailable. Continue running matches and saving results in the desktop app; a publication failure does not roll back those local changes.

If a publication fails:

Keep working locally if publication is not immediately required.
Check the saved token and network connection.
When the connection is stable, select Publish manually.
Wait for a new successful-publication time.
Open the public link separately and verify the information you need visitors to see.

The publication request times out after 15 seconds. A timeout means that the app did not receive a success response in time; it does not by itself prove what the service received. Retrying builds a fresh complete snapshot for the same tournament identifier and same public link. A later successful retry replaces the public representation with that newer snapshot rather than creating a second tournament link.

Check before publishing

Confirm the tournament name, dates, manual status, venue, and organizer contacts.
Review accepted, pending, and rejected registrations; only accepted registrations enter the snapshot’s player list.
Check event entries, pair membership, Partner Wanted records, and seeds.
Review draw membership, round-robin standings, and playoff progression.
Confirm match sides, statuses, winners, set scores, scheduled times, and courts.
Review final places, player event points, and tournament-points rules.
Check that the intended publish token is saved.
For an update, decide whether a manual publication is needed because the Match day badge does not cover every snapshot field.
After success, check the displayed time and verify the public link separately.

Fix common problems

Publish or Auto is unavailable

No publish token is saved. Open Settings, enter the token, and leave the field to save it. Then return to the tournament. Auto also requires a successful manual publication from Match day before it can detect changes.

The token is reported as invalid

The service rejected the saved token. Obtain the current token from the site administrator, replace Publish token in Settings, leave the field to save it, and retry.

Publishing times out

The app did not receive a response within 15 seconds. Check the connection and retry manually. If the first request reached the service despite the timeout, the successful retry still sends a complete newer snapshot to the same tournament link.

A network error appears

The app could not complete the request. Keep operating the tournament locally, restore the connection, and publish again. Local results and tournament changes remain saved.

A server error appears

The service returned an unsuccessful response other than an invalid-token response. Wait and retry. If the error continues, contact the site administrator and keep the local tournament as the authoritative working copy.

Auto does not publish

Check that the token is saved, Auto is selected, a successful manual Match day publication created the local baseline, and the +N badge is above zero. Allow at least one minute after the previous success or automatic attempt. If only an untracked field changed, publish manually.

The badge is missing

There is no local Match day baseline on this device. Select Publish manually from Match day. Publishing from Overview does not create the badge baseline.

The badge stays at zero after an edit

The edited field is not part of the Match day comparison. Court, scheduled time, entry, draw, standings, and tournament-detail changes do not increase the badge by themselves. Use Publish manually.

The displayed publication time seems old or disappears

Overview remembers the time only while its current panel remains open. Match day loads the time from its device-local baseline. Neither display queries the public page, and an error message can temporarily replace the visible time. Publish successfully again, then verify the public link separately.

The public information does not match the desktop app

Confirm that the most recent attempt succeeded, then publish manually to send a complete current snapshot. Remember that the badge compares only selected match changes and that the displayed time is not a live public-page check. Open the public link after the success response to verify the required information.