I purchased some new shares today, and the app seemed to struggle to calculate the new Investments.
It should have showed roughly £1950 total, however it was saying £2150ish. Now it has corrected itself however the graph shows a big spike, which clearly wasn’t due to stock price movements.
See screenshot for a one day chart:
Yep mine did this as well, is there any way this can be fixed?
I’m guessing you bought approx £200 worth of shares? Mine does this occasionally too. Seems to be that the assets get allocated, the reserved cash is not taken down immediately, thus a short window when you have both. Would have thought a DvP (delivery Vs payment) type mechanism in the app should stop this from happening/displaying, but at least you don’t have a short window where you have neither!
Agreed it looks fugly for the beautiful graph, get used to seeing that hump in all your timeline graphs.
I think you might be right.
Just realised I got my numbers wrong, I had ~£1450, and invested in ~£500 of shares. So the £1950 total is the correct number.
£100 of shares failed to buy, I guess that’s why it didn’t add all the cash and investments twice and show ~£2500
Any reason why you’ve gone for the Vanguard S&P 500 over the iShares - it’s 0.001% more expensive 
Is there much difference to be honest?
Mine did this too! Value of the stock purchase was added to portfolio before the money was taken… I’ve just ignored it for now
I have also had this happen at one point in my graph around 2 months back. It drops down about £1600 and then bounces right back up so my graph has an odd spike it in.
Hi,
This is unfortunately a known issue with the display of portfolio data for some users. Occasionally when placing an order, there may be a delay between the movement of money and the movement of shares in your portfolio, this results in a temporary spike or dip in your portfolio graph. Sincere apologies, it isn’t up to standard and we’re working on improving it!
The first important point to note is that there was (and always is) a correct record of your portfolio in our backend systems. This is an (admittedly ugly 
) display issue when syncing the data for display in-app.
Our plan for resolving this issue is:
Hope that helps and apologies again.
Awesome and clear response, thanks Tim 
I think everyone is SUPER excited for the new investment platform. Can’t wait to see it!
Hi Parrish,
Ouch, yes you certainly are still getting it, apologies we haven’t shipped a fix for this yet. We’ve had a couple of design sessions discussing a fix but didn’t make significant progress. I’ve mobilised one of our engineers who is looking at a solution for this right now, I’ll come back next by this time next week with an update on how we’re moving this forward.
In the meantime if you get in touch with our customer ops team, we can get those spikes tidied up for you.
Apologies again for the delay on this.
I appreciate the reply Tim. I’ll keep an eye out for a further update. Thanks
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.
Sounds like a sufficient tactical fix till the strategic solution of the new platform arrives!
Will the routine be backwards looking and sort out historical spikes, or only squish those caused by trading on the specific day? I haven’t asked for mine to be squashed as I thought that the ops team probably have more important queries to deal with.
Hey Tim, any update on the automated routine to fix these display issues?
