Time for an update! We’ve discussed this at length internally within the engineering team.
The bad news is that this is a systemic issue with our 3rd party provider integration, so we’re not going to be able to 100% resolve it till we cut over to the invest platform. It is frustrating that this kind of thing is even an issue, just one of the many reasons we’re building the new platform.
The good news is that we’ve come up with a routine that will correct these spikes automatically, we’re testing the routine internally right now with plans to roll it out to all customers within the next couple of weeks. It won’t pick up everything, and you might still see spikes until the routine runs, but it should be a significant improvement on the current experience.
Apologies again that this is even an issue, we’re doing what we can to mitigate it now whilst also working towards a permanent fix.