You keep adding requirements, so more work is needed.
Multiple screens can't talk to each other.
TinyDB is easier than CloudDB for local storage, and you should be able to distinguish between the two and know where to use one and where to use the other.
All username and score information must be available before attempting to update it.
The screen Initialize event is a good place to ask for the latest high score list.
It should arrive before the user has a chance to enter his name and confirm.
There is a red X in your blocks image, in the gethighscores procedure.
That procedure is incompatible with storing scores and names in a table.
I advise removing that procedure.
You have fallen for the sunk cost fallacy, where you have devoted so much time and money into something that won't work, that you are reluctant to give it up.
i save as copy and run with other projectId for cludDb, now it turn to this result ( show only 1 value, and keep replace it when it is higher than the existing value)