indexer
indexer copied to clipboard
update action statuses and indexing rules
As reported in issue #575, we observed cases in which the agent allocate to a subgraph deployment right after unallocate actions. The two possible causes are
- allocation was closed successfully but failed to confirm due to IE053 when identifying the receipts, thus exited with error early without updating the indexing rules
- moved update indexing rules to right after closing allocation, and before identifying receipts to collect. Regardless of the result for query fee collection, the indexing rules should be updated promptly
- transaction to update action statuses did not include all the approved actions, might be due to agent creating allocate actions too early from indexing rules
- added an additional step to update actions not included, and added debug logging