AppConfigData / Client / exceptions / BadRequestException

BadRequestException#

class AppConfigData.Client.exceptions.BadRequestException#

The input fails to satisfy the constraints specified by the service.

Example

try:
  ...
except client.exceptions.BadRequestException as e:
  print(e.response)
response#

The parsed error response. All exceptions have a top level Error key that provides normalized access to common exception atrributes. All other keys are specific to this service or exception class.

Syntax

{
    'Message': 'string',
    'Reason': 'InvalidParameters',
    'Details': {
        'InvalidParameters': {
            'string': {
                'Problem': 'Corrupted'|'Expired'|'PollIntervalNotSatisfied'
            }
        }
    },
    'Error': {
        'Code': 'string',
        'Message': 'string'
    }
}

Structure

  • (dict) –

    The input fails to satisfy the constraints specified by the service.

    • Message (string) –

    • Reason (string) –

      Code indicating the reason the request was invalid.

    • Details (dict) –

      Details describing why the request was invalid.

      Note

      This is a Tagged Union structure. Only one of the following top level keys will be set: InvalidParameters. If a client receives an unknown member it will set SDK_UNKNOWN_MEMBER as the top level key, which maps to the name or tag of the unknown member. The structure of SDK_UNKNOWN_MEMBER is as follows:

      'SDK_UNKNOWN_MEMBER': {'name': 'UnknownMemberName'}
      
      • InvalidParameters (dict) –

        One or more specified parameters are not valid for the call.

        • (string) –

          • (dict) –

            Information about an invalid parameter.

            • Problem (string) –

              The reason the parameter is invalid.

    • Error (dict) – Normalized access to common exception attributes.

      • Code (string) – An identifier specifying the exception type.

      • Message (string) – A descriptive message explaining why the exception occured.