# Undos

UNDOS NO LONGER RETURNED.

This packet will be sent to indicate that the previous packet has been undone. Multiple undo packets indicate that multiple things have been undone. Undos are always sent in sequence.

(20/12/2018 – this may be subject to slight change but this is the working model we have at the moment)

**Undo Object**

| Field Name       | Type    | Description                          |
| ---------------- | ------- | ------------------------------------ |
| seqNum           | integer | The sequence number of the packet    |
| timestamp        | date    | The timestamp of the event, in UTC   |
| eventElementType | string  | The type of event, in this case Undo |

\
**score Object**

This contains information on the player’s score at this time. If the undo changes the player’s score, this will be reflected in this packet, if not the score will not change but will still be included in the packet.

| Field Name         | Type    | Description                                                  |
| ------------------ | ------- | ------------------------------------------------------------ |
| currentHoleStrokes | integer | the number of strokes the player has had on the current hole |
| currentHolePar     | integer | the par of the current hole                                  |
| currentRoundToPar  | string  | The “to par” score of the player’s current round             |
| overallToPar       | string  | The “to par” score of the player overall                     |

\
**Sample Event Packet**

```
{
	"score": {
		"currentHoleStrokes": 6,
		"currentHolePar": 4,
		"currentRoundToPar": "+1",
		"overallToPar": "-2"
	},
	"eventElementType": "Undo",
	"timestamp": "2018-07-31T10:42:02.078Z",
	"seqNum": 198
}
```

## Doc navigation

[← Hole Score Update](https://docs.sportradar.com/golf/round-details-scenarios/hole-score-update)