If a timer is having trouble with auto-saves publishing/updating properly to RunSignup there are a few troubleshooting steps that can be taken to correct this. These troubleshooting steps are listed below in the order that they should be tried, from the simplest fixes to those that require the most work and correction. Before going down the path of troubleshooting, it is worth confirming that your reads are being considered properly, that you have an Actual Start Time set, and that your report has data in it in the first place.

Step 1: Confirm that Auto-Saves are On (and you are connected to the Internet)

While this seems fairly self-explanatory, checking to see that you have turned on Auto-Saves should be the first step to making sure reports are publishing and updating properly on RunSignup. This is as simple as making sure the indicator on the Auto-Saves connector is green:

If it isn't, simply click this button to turn on Auto-Saves. Note that if you are not connected to the internet, this button will still be green (as you can be running local auto-saves of files) but you will see a red banner indicating that you aren't online:

Step 2: Check that an Auto-Save is set up (and that you aren't using Quick Publish)

The first indication that you have an Auto-Save set up is that a "Live Results Link" button will be visible for the report you are sending to RunSignup:

To confirm, you can click "Auto-Save Settings" and ensure that you have a stream set up:

If you do not see a stream here, set one up.

It is also possible that you have used Quick Publish instead - Quick Publish reports do not automatically update and require the user to click "Quick Publish" each time they want to update the report on RunSignup. You can see that a report has Quick Publish set up at a glance by seeing if there is an additional "Quick Publish" button associated with that report:

Quick Publish reports do not update Auto-Save reports (and vice-versa). 

Step 3: Use the Participant and Result Sync

If you do have a report that is set to auto-save, auto-saves are correctly set up, and the report is still not displaying properly, simply click the Participant and Result Sync button in the upper right-hand corner of the RaceDay Scoring window:

Step 4: Edit the Auto-Save Stream and Re-Save

If this still does not work, you may need to delete the Auto-Save to RunSignup stream and re-add it. This is done by going to the Auto-Save Settings for the report and clicking the X on the RunSignup Results stream:

You will be asked if you want to remove results from RSU, Leave Results at RSU, or Cancel. You will also be prompted to indicate if you wish to Delete Divisions Setup for Event [eventname] at RunSignup as well:

This choice is up to you - keep in mind you can map a new Auto-Save Stream to an existing results set - keep in mind that deleting a results set will potentially break some links going directly to that set's URL:

The order of operations here would be to delete the stream, save the Auto-Save, and add the stream back again.

Step 5 - Delete the Report and Rebuild it

This is the last step here because it takes the most work, and includes most of what has already been covered all at once. You can skip right to Step 5 if you are comfortable enough, but it is more involved. To delete an existing report (even if it has auto-saves associated with it), go to Actions -> Delete:

If there are Auto-Saves associated with it, you will have similar options to removing an Auto-Save Stream, with the same caveats:

You can then Build a New Report and add it as an Auto-Save. The default report section for an event without teams is an Overall Section, while the default report for an event with Team Scoring is an Overall Section W/Teams.

Addendum: If the report itself is not working as expected and re-saving the Scored Event Settings fixes the issue in RaceDay Scoring, it's likely that the Auto-Save will work straightaway without having to edit and re-save the Auto-Saves as saving Scored Events doesn't update the structure of an existing report.