I a new portfolio with some transactions and at first the portfolio worked fine. However, the portfolio holdings subsequently stopped updating. I even deleted the portfolio and re-created it by importing the prior transactions, and now it doesn’t even show any holdings.
This now seems to affect all my portfolios. I’ve left it to run overnight, but still no changes.
I’m not sure if it’s relevant but:
a) some of the transactions involve a delisted stock (T8JU) which was listed in red (which I initally imported into the new portfolio, then later moved the transactions into an existing portfolio)
b) another portfolio has a CASH holding, also listed in red and whose value differs from the Cash Balance displayed in the summary. This only shows up when I view that specific portfolio and not when I select multiple portfolios.
Yes, given the current setup. It is possible that the update is delayed up to a few minutes when the queue is loaded.
We have a few options.
Block user when adding transactions. Only load page when the added transaction is processed. (This might be irritating for users with multiple transactions to add)
Clearly show users when they have something in the queue. So that they know it is pending update. (This is similar to what is happening now except showing a display to explicitly state it)
Create another queue dedicated to processing transactions updates only. (This could be a waste of resources when there are no updates and in the extreme case if many people updating at the same time, might still face same issue)
Been using quite some years and never have issue until of late.
If you prefer point2, then you do not need to do anything as after I added a new transaction, that counter in portfolio do have small arrow red either up or down next to it.
This arrow indicator (up or down) have been there together with updated lesser or more qty stock upon add transaction.
Anyway I will take note and leave decision to you.
Yes, I only switch from Point 1 to current queuing style around 1-2 years ago which is why the first reported date is May 2023.
Hence I am reluctant to switch back to point 1 because it has it own set of problems. Guess point 3 is best then. Maybe I should consider point 4 which is like point 3 but instead of another queue, reuse the same queue but with different priority.