Deploy operation reported as failure even if it was successful

I've created a new servergroup 'frobnitz' with one managed AS that was not started.

I have deployed a war to it and get a failure back.
This makes on one side some sense, as it was not applied to the downed host, but as the war was applied to the SG itself, it should get a different kind of result:
After I have started the managed AS, the war file got successfully installed in it and deployed and I can call it as it should.

I think the scenario of deploying stuff to downed AS is common in scenarios, where you only want to start machines on demand when the load increases.

Upload:
{"outcome":"success","result":

{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="}

,"compensating-operation":null}

Adding + deploy:
Json to send: {"steps":[{"address":[

{"deployment":"test-simple.war"}

],"operation":"add","runtime-name":"test-simple.war","hash":

{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="}

,"name":"test-simple.war"},{"address":[

{"server-group":"frobnitz"}

,

{"deployment":"test-simple.war"}

],"operation":"add","enabled":"true"}],"address":[],"operation":"composite"}

Return value from the domain:
==> {"outcome" : "failed", "result" : {"server-groups" : {"frobnitz" : {"myDemo" : {"host" : "local", "response" : {"outcome" : "failed", "failure-description" : [

{ "java.lang.IllegalStateException" : "No handler for add at address [\n (\"host\" => \"local\"),\n (\"server\" => \"myDemo\"),\n (\"deployment\" => \"test-simple.war\")\n]" }

]}}}}}, "failure-description" : "Operation was not applied successfully to any servers"}