# Synthetic Monitoring Clickpath Actual vs Expected Threshold

**URL:** <https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350>\
**Category:** Synthetic Monitoring\
**Tags:** browser-monitors, synthetic-monitoring\
**Created:** [October 15, 2024, 6:35pm UTC](https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350 "2024-10-15T18:35:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vuthayak](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vuthayak](https://community.dynatrace.com/u/vuthayak)\
**Post date:** [October 15, 2024, 6:35pm UTC](https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350/1 "2024-10-15T18:35:27Z")

</div>

Hi all, I wanted to know if there is a way to set up a threshold for the difference between the actual vs expected screen captures for a clickpath. In the image below, the synthetic monitor occasionally throws a false positive error, since the phase of the loading icon is slightly different (0.13% difference). If there isn’t any way to implement a threshold, is there a workaround that those in a similar position have used? Thanks.

 ![vuthayak_0-1729017248195.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/d/6dae9f9b5fc2cfe3973133fe87da7646b9f6448e.png)

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [October 15, 2024, 11:11pm UTC](https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350/2 "2024-10-15T23:11:24Z")

</div>

Hi&nbsp;[@vuthayak](https://community.dynatrace.com/user/81972)&nbsp;, you seem to be getting 1304-&nbsp;Wait for Page Complete Timeout/ Time exceeded waiting for page to load completely error .

You&nbsp;can set performance thresholds and alert for total duration or for individual page events , see below

> **[Configure browser monitors in Classic](https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/browser-monitors/configure-browser-monitors)**
>
> Learn about configuring browser monitors and clickpaths.

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [October 16, 2024, 6:19am UTC](https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350/3 "2024-10-16T06:19:00Z")

</div>

Hello&nbsp;[@vuthayak](https://community.dynatrace.com/user/81972)

- If you have the application&nbsp;monitored in Dynatrace, you can observe it’s performance metrics and customize the performance thresholds accordingly.
- If you have access to edit the synthetic monitor configurations, you can customize the performance thresholds for the synthetic monitor as per the shown error it’s page load complete timeout.

 ![2024-10-16_10h07_56.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/a/6a0e6867c0f66090c010eded9cc66e59a4612a2d.png)

You can also get detailed guidance provided by Dynatrace&nbsp;[browser-monitors-config#performance-thresholds](https://docs.dynatrace.com/docs/shortlink/browser-monitors-config#performance-thresholds)

KR,

Peter.

---

<div class="post-metadata">

**Author:** ![Fin\_Ubels](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fin_ubels/32/18008_2.png) [@Fin\_Ubels](https://community.dynatrace.com/u/Fin_Ubels)\
**Post date:** [October 17, 2024, 3:47am UTC](https://community.dynatrace.com/t/synthetic-monitoring-clickpath-actual-vs-expected-threshold/48350/4 "2024-10-17T03:47:58Z")

</div>

Hey&nbsp;[@vuthayak](https://community.dynatrace.com/user/81972)

I don’t think it’s the difference in the page that’s causing the synthetic failure. It’s just showing that there is a small difference between expected and captured after it failed.

Based on the error, it looks like the page is taking longer than 60s to load which then causes the synthetic to timeout and fail.
