Powerup transactions return "executed" but don't show up in the blockchain

[CherryDT]

trafficstars

This is possibly a duplicate of #10239 but the other issue was already closed and I started experiencing this only recently and not since April.

The problem is that buying CPU with powerup seems to succeed, it returns state executed and I get a TX ID (both if I do it using my own node.js code and if I do it with Anchor Wallet), but the TX never shows up on the blockchain, and the resources never arrive.

What can be the issue?

EDIT: Today it worked - 3 days ago it didn't work (I tried many times), weird. Still, I'd like to understand what went wrong here and how I can handle it / make sure it won't happen again...

[deckb]

There are a couple of reasons why a transaction would succeed locally and fail to be put into a block. Some of the reasons are outlined in the docs.

There is also the idea of subjective billing that was introduced in 2.0.10 that could cause a transaction to fail to be relayed to a producing node.

In regards to a failure specific to the powerup transaction one of the issues could be that the nodes relaying the transaction could calculate that the amount of resources that would be given to the account do not cover the cost of the powerup action. If the account doing the powerup action has 0 resources the amount of resources being reserved by the powerup action must at least cover the cost of a powerup (which is roughly ~200us).

[CherryDT]

It's again happening now. Both in Anchor and in my own code. My own code is trying it every 5 minutes and there was no successful powerup for 90 minutes now.

I think I understand what you explain about the node miscalculating resources, but I don't understand what I can do about it. The node is eos.greymass.com (it resolves to 88.198.5.198), I don't control it. What are my next steps to solve this problem?

[heifner]

I would contact eos greymass and see if they can provide you with information on your transaction.