Yes, I do - attached is a grab of the base task. I also ran trains.get_task(*params).id to make sure the task id's matched, in case a did something stupid. They did some I'm guessing it has something to do with the way I am implementing the optimization itself, but all my code is boilerplate for my toy example.

CharmingBeetle38 try adding "General/" before the arguments. This means batch_size becomes General/batch_size. This is only because we are accessing the parameters externally, when the task is executed it is resolved automatically

Hi CharmingBeetle38
On the base task, do you see those arguments under the Configuration tab?
Also, if they are under Args section, you should add "Args/" prefix to the HP optimization (this is how you differentiate between the sections)