Skip to content

Commit dd07cd5

Browse files
author
Adam Dupaski
authored
Merge pull request mendix#6535 from mendix/ad-session
Proofread example
2 parents 587000d + 8632e06 commit dd07cd5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/en/docs/howto7/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This how-to will teach you how to do the following:
1414

1515
* Find the root cause of runtime errors via two methods
1616

17-
## 2 Method 1 – Using the Modeler
17+
## 2 Using the Modeler
1818

1919
If the application is deployed from the Modeler, the information is located in the console:
2020

@@ -32,7 +32,7 @@ There are three key pieces of information in this window:
3232

3333
With these three pieces of information, you should be able to find the cause of the error. If you cannot determine the cause from this information, you can put a break point in the specified microflow and debug the situation.
3434

35-
## 3 Method 2 – Using the Application Logs
35+
## 3 Using the Application Logs
3636

3737
If the application is deployed from the service console or in the cloud, the information is available in the application logs.
3838

0 commit comments

Comments
 (0)