Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Setting breakpoints in the Tracer tool

Updated on January 14, 2022

You can set breakpoints to pause processing for specific steps in activities. When you set a breakpoint for an activity, the Tracer window acquires focus when you or the selected requestor connection starts the activity.

For example, if a step in an activity triggers a data transform, you can set a breakpoint before the step so that you can analyze and understand how the system updates the values in the data transform.
Note: If you build your application on Cosmos React, Tracer does not support breakpoints. Changing configurations for breakpoints in Cosmos React applications might cause issues.
Note: You cannot view the clipboard when the system reaches a breakpoint during processing because the requestor that the Tracer traces pauses.
  1. In the footer of App Studio, click the Open runtime toolbar icon, and then click the Tracer icon.
  2. On the Tracer toolbar, click Breakpoints.
  3. In the Class Name field, select the Applies To class that stores an activity to trace.
  4. In the Activity Name field, select an activity.
  5. In the Where to Break list, select one of the following options:
    • To stop processing when the activity starts, select 1.
    • To stop processing before a specific step, select the step number.
    • To stop processing before every step, select all steps.
  6. Click Set Break.
  7. Optional: To add more breakpoints, repeat steps 3 through 6.
  8. Optional: To remove a breakpoint, in the Remove column, select the check box, and then click Remove.
  9. Click Close.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us