When the dashboard says an upload was refused

The reasons this product turns an upload away, the six that are yours to act on in the dashboard's own words, and what happens with the rest.

Where you see it

When something your connector sent was turned away, the dashboard says so at the top, names the reason, and offers a ticket already filled with it. A refused trades file means a session is missing; a refused market file means a session arrived thinner than it should have. The dashboard knows twenty one reasons. Six of them end with something you do; every other one ends with the ticket the dashboard offers, and that sentence says so itself.

The six that are yours to act on

"a pairing code we do not recognise." Your connector introduced itself with a pairing code this account does not know, so nothing it sent could be filed. Pair it again on the setup page: the code it holds was replaced or was typed with a character missing.

"a pairing that was revoked." Your connector is still using a pairing that was revoked, so everything it sends is refused. Pair it again on the setup page and it picks up where it left off.

"an account on its way out." Your account is inside its deletion window, and nothing new is accepted while that runs. Sign in and press Keep my account to call it off.

"a file that is not a Trading Statistics export." The file your connector sent is not a Trading Statistics export. That usually means the folder it watches holds something else: check the setup steps, and tell us if it looks right to you.

"an export we could not parse." Your connector sent a Trading Statistics export we could not read to the end, so the session in it was not filed. Tell us and we will ask you for that one file: an export we cannot read is something we want to see.

"an instrument outside futures." The file was for an instrument this product does not cover: AI Gary reads futures. Your connector has stopped sending that one, and everything you trade in futures still arrives normally.

The rest are ours

The other fifteen name something on our side: more uploads at once than we accept, a file over the size we accept, an upload we could not read, an append we refused, a market file we refused, a file name this server does not know, our own failure while storing, our own read of your pairing or of where your file stands failing, an addon file this server does not accept or does not store, a line from a copy of a file we had already retired, and more data at once than we hold. Each of those sentences ends the same way: tell us. The ticket the dashboard offers is already filled with the reason, so press it, add anything you saw, and send. Three of them ask for something first: a file name this server does not know and an addon file it does not accept both want the addon and the connector updated from the setup page, and our own failure while storing wants telling straight away, because your connector keeps retrying that file and can hold back the ones behind it.

One of them ends differently on market data and on the addon's record of your orders. When what was turned away for more uploads at once than we accept is one of those, nothing is lost: your connector keeps it and sends it again on its own until we take it, so it only arrives later. It is only worth telling us about if that count keeps climbing. A trades file turned away for the same reason is not retried: it goes again only when Bookmap rewrites it or your connector next starts, so that one does want telling.