Oh ok, thanks :D  It returns a 202 even if the webhook itself is completely invalid actually, or if it's valid and the launch config is broken.

Actually executing scaling policy will return 202 if the launch configuration is broken too, because it doesn't wait for the servers to spin up before returning.  Just fails if there's an accounting (min/max, cooldown, etc.) error.