As title suggests, the actions queue isn't propagated to the indexer agent
root@77ce1a92c513:~/scripts# graph indexer actions get
✔ Processed input parameters
✔ Actions query returned
No actions found
root@77ce1a92c513:~/scripts# cd ...
bash: cd: ...: No such file or directory
root@77ce1a92c513:~/scripts# cd ..
root@77ce1a92c513:~# cd optimizer/
root@77ce1a92c513:~/optimizer# cd bin/
root@77ce1a92c513:~/optimizer/bin# nano config.toml
root@77ce1a92c513:~/optimizer/bin# ./AllocationOpt config.toml
[ Info: Querying data from https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum
[ Info: Writing table to ./indexer.csv
[ Info: Writing table to ./allocation.csv
[ Info: Writing table to ./subgraph.csv
[ Info: Writing table to ./network.csv
[ Info: Optimizing
[ Info: Writing results report
[ Info: Executing best strategy
root@77ce1a92c513:~/optimizer/bin# graph indexer actions get
✔ Processed input parameters
✔ Actions query returned
No actions found
root@77ce1a92c513:~/optimizer/bin#
As title suggests, the actions queue isn't propagated to the indexer agent
Config:
The report does indeed have the actions, but they're simply not propagated to the agent