so I’ve done a bulk upload of basically all my activations made before 2024-05
after uploading and when planning possible new activations I have noticed a S2S contact that had a wrong date for the summit i chased (“shifted” to the next activation date)
after further looking into it I discoverd that some(how) apparently s2s contacs have wrong dates in the database though beeing shown correctly if i click edit.
as an example - here is one of the (2) dates I have found this error at (already):
If I didnt miss anything, the edit view of the uploaded data and the actual file i have in my PC have consistent (and correct) data and only the final/public log has the date-error.
is there anything i am not aware of I could try to solve this problem or should i just delete and upload again? (maybe separating to individuall activations?)
We use a pair of servers and a load balancer to split the DB reading and writing. All apps accessing the DB use the servers and the load balance spreads the load. If one server fails, we still have the other and the load balancer only sends work to the working server. What doesn’t work is when one server runs out of disk space. It can’t work properly but appears to be working from the load balancer’s view. Then it’s random which server anything goes to. The log rotation code was broken so one server was out of disk space. If your uploads where handled by this server they would appear to work but would be wrong.
Andrew cleaned up the disk space and apart from an typo error in the ADI file, he could not make it fail. When I tried I split the ADI into 3 CSVs and it worked for me. I was probably hitting the good server.
You need to do 2 things.
Delete the upload you made with the Manage Upload page.
