Gateway Time-out when awaiting tip/retip

[davidyuk]

It seems that tracking of at least v1 tips/retips is broken, we found it by dropping error omitting in aeternity/superhero-ui#1133. From my perspective, these endpoints should never return 504 if it is called right after submitting a tip. As a workaround, I would omit exceptions from there, but fixing it would speed up making a tip/retip.

[ifaouibadi]

We're facing this issue again, it's taking a long time for the tipping backend to check if tip/retip exists, and it's throwing a Not Found exception while the tip/retip actually gets created and appears in the feed after 2-3mins

[thepiwo]

There is supposed to be a timeout after 30s, if we haven't received it by then something is probably wrong or we can't ensure the event hasn't already happened and we missed it.

For consumers they can choose how to handle this, e.g. by just reloading when there has been a timeout on this endpoint