anchor.diff:  * *Headers* to provide a custom list of HTTP request headers.
   * *Request body* to configure a custom request body. 
   
  -Since debug mode emulates an external call to your API, it will resolve the flow as the gateway would do, so if you want to debug a specific flow you must configure your request (path, headers) to replicate the conditions at which the flow is triggered.
  +Since debug mode emulates an external call to your API, it will resolve the flow as the gateway would do, so if you want to debug a specific flow you must configure your request (path, headers) to replicate the conditions on which the flow is triggered.
   
   image:{% link images/apim/3.x/api-publisher-guide/design-studio/debug-mode/debug-mode-example.png %}[Debug Mode example]
   
  
positive.code: 
  image:{% link images/apim/3.x/api-publisher-guide/design-studio/debug-mode/debug-mode-example-empty.png %}[Debug Mode empty example]
  
  The embedded HTTP client let's you configure different attributes of your request:
  
  * *HTTP method* to select the HTTP verb (e.g., `GET`, `POST`, `PUT`, etc.).
  * *Path* to test a specific subpath and provide query parameters. 
  
negative.code: image:{% link images/apim/3.x/api-publisher-guide/design-studio/debug-mode/debug-mode-legend.png %}[Debug Mode legend]
  
  * *executed* - the policy has been executed properly
  * *skipped* - the policy contains a condition that has not been fulfilled. Refer to the input/output inspector for more details on the evaluation of the condition.
  * *error* - an error occurred during policy execution. Refer to the input/output inspector for more details on the error.
  
  By selecting a specific policy in the timeline, you have access to additional information regarding the input/output of the policy:
  