Collecting stats and errors

Earlier in this chapter, we looked at the built-in performance monitoring facilities in OmniStudio as well as the Vlocity Tracking Service. These are the go-to tools for getting performance-related data. Now, what do we do when things are not working as expected, when our code breaks, or when we need to do some quick troubleshooting? In the following section, we will look at tools we can use to dig in and find bugs and reasons for sub-standard performance that are hiding deep below the surface.

Let’s begin with every developer’s go-to tool: Salesforce debug logs. Let’s see how debug logs can come in handy when debugging OmniStudio issues.

Salesforce debug logs

Debugging OmniStudio solutions at times can be very straightforward, while at other times it can be difficult. Let me share a couple of tricks we like to use to locate the offending component when troubleshooting errors for our clients. Let’s look at a couple of...