You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When querying a transaction result using the AccessAPI, the logic will first check if the node knows about the transaction from indexing the collection it was included in. If not, the API will return not found. This means that there may be a delay after the tx was executed while the Access node syncs the collections from collection nodes.
In the case of the SendAndSubscribeTransactionStatuses endpoint, it would be great if we could notify the client immediately after we detect that the block was executed.
Investigate if this is possible and write up a proposal for how it would be done.
The text was updated successfully, but these errors were encountered:
When querying a transaction result using the AccessAPI, the logic will first check if the node knows about the transaction from indexing the collection it was included in. If not, the API will return not found. This means that there may be a delay after the tx was executed while the Access node syncs the collections from collection nodes.
In the case of the
SendAndSubscribeTransactionStatuses
endpoint, it would be great if we could notify the client immediately after we detect that the block was executed.Investigate if this is possible and write up a proposal for how it would be done.
The text was updated successfully, but these errors were encountered: