@monteiro Default deployment is not optional in the configuration. Also we expect the default deployment to be one of the deployments defined below in the configurations.

What will be the default when default doesn't match the configured deployments below? (Say, user has a default deployment that functions only for the failed requests). But logically, that doesn't sound real. User should define his deployments properly in the configuration, for the weighting algorithm to function properly.

Probably in the later versions, we should consider an error handling for malicious sysadmins. 

I don't find a logically correct default label, when the default is not defined to match one of the deployments in the config.json.

@leolara