Closed fordN closed 1 year ago
Thanks Ford! the above error was solved by changing the config input to use actionqueue
as specified in the docs (instead of actionQueue
)
We can make UI improvements by validating all the fields in the provided config before running the optimizer
It was indeed not a bug, but a configuration issue on my end! Thanks for help resolving quickly!
When running the optimizer in
actionQueue
mode I run into the following error. I had no issues inrules
mode.I'm using the latest indexer software (main branch) and the following allocation-optimizer config.