Troubleshooting strategy rules by using the Tracer tool
You can use the Tracer tool to view the order in which the top-level strategy and its substrategies are processed in your application. The outcome of the analysis can give you insight about the correctness of the strategy configuration.
For example, with the Tracer tool, you can detect a faulty switch condition that prevents a substrategy from running or that unnecessarily triggers a substrategy.
Using the Tracer tool to view the order in which strategies are processed
- In the navigation pane of Dev Studio, click Records.
- Expand the Decision category, and then click Strategy.
- From the rule list, select a strategy to analyze.
- Click Tracer to open the Tracer tool.
- In the Tracer window, click Settings to open the Tracer Settings window.
- In the Event types to trace section, select Strategy.
- Click OK to save the trace criteria and close the Tracer Settings window. Do not close the Tracer tool.
- On the Strategy form, click .
- In the Run window, click Run.
- In the Tracer tool, analyze the run results.
For example: By using the preceding procedure, you can analyze the following multilevel strategy: Example of a strategy with multiple layers of substrategies 
When the strategy is run, it returns the following results in the Tracer tool:
Multilevel strategy sequence of processing as seen in the Tracer tool 
The results show that the application processes the strategy in the correct sequence. The strategies started in the following order: S1, S2, S3. The strategies were completed in reverse order: S3, S2, S1. This behavior is a result of the following strategy configuration:
- Strategies are processed in descending order from the top-level strategy.
- A strategy finishes processing after all its substrategies are complete.
Previous topic Troubleshooting proposition filters Next topic Troubleshooting the strategy test run panel