Retries
- Transactions: resend with the same
id. A repeat never creates a duplicate. If the repeat has the samestatusas the stored transaction, it updates the transaction. Otherwise Konsol ignores it. For example, once an approved void marks a sale as voided, resending the sale changes nothing. - Hourly totals: a report for the same hour replaces the earlier one,
whatever its
id. - Events: resend the same batch unchanged. Events accepted in the last 7
days are answered
duplicate. Older repeats are answeredaccepted, and still create no duplicate. - Reads and download URLs: safe to repeat at any time.
- Heartbeats: send a new heartbeat with current data rather than repeating an old one.
- Activation: after a
500, get a new activation code. The earlier code may already have been used.