ehamery

Have you considered including that check in the `block()` function? `this.connex.thor.status.head.number` should never be `null` or `undefined`... `await this.connex.thor.block().get()` sometimes returns null. That is the same issue, isn't it?

If you do not provide any argument to the `block()` function, `await this.connex.thor.block().get()` should return the head block, so it should never be `null` and it sometimes is. That looks...

I am basically scanning blocks and once in a while `await this.connex.thor.block().get()` returns `null`.

I did not keep the whole transaction ID because it is not specific to that transaction, it happens once in a while on different transactions.

``` $ curl -vvv https://vethor-node.vechain.com/transactions/0xab5e6f13f9ae28e5d7bbc11058280a9906ac29091398402302b85b732a6fb583 * Trying 128.1.34.13:443... * Connected to vethor-node.vechain.com (128.1.34.13) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations:...

How do I do a "diagnosis"?

> This seems no problem. Maybe do a diagnosis when you got the same problem. Of course there is no problem here, as I said above `it happens once in...

> It's a connection issue, depends on your network setup, the public node setup. `curl -vvv` is the way to do the diagnosis. How can you say that without reproducing...

> I did not keep the whole transaction ID because it is not specific to that transaction, it happens once in a while on different transactions. So the answer is...

@qianbin Is there any chance to get this PR reviewed and merged?