Yes, and I can explain why.
The page polls each interval to retrieve the list. It doesn't get the list in one go, each polling is a network request - the response contains a number indicating percentage done.
Whatever the triggering issue, the polling can always return 0 - meaning continues polling.
I've no access to the code, so can't comment why it's happening.
I've made an assumption as to the way this works, and have suggested may a different approach to doing it all. It's up to JDB to decide if what I proposed is viable or useful.
The draft was working fine for me hours ago, it could be potentially a load issue that starts the problem.
