Hello,
We are trying to capture parameters in response to recipient form while the page loads in chrome, but in the table the records are captured twice for a single load.
We are using storage activity before the page activity, with the action of update/insert in storage activity.
Is there any way we can avoid the duplicate entry of records for a single load of page.
Thankyou!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
I have a feeling that you are testing this on a non-prod environment.
Please copy the webapp link from your test email sitting in your inbox. Open Chrome developer tools and go to network tab and enable Preserve Log.
Now paste the copied URL and hit return
You might see the tracked URL from your email being invoked twice.
We've seen this happening many times when there are security softwares installed inside your work VPN or office which first resolve the URL to ensure that it is not an invalid page and only then send the request again. If this is the case for you, it is expected and you cannot bypass it, unless your IT team starts trusting the non-prod environment emails or links.
Hi @laksh1519 ,
Two records indicate that the webapp is invoked twice. You will have to review your webApp implementation.
It could be happening when your WebApp is being loaded and form is presented(1st insert) and when form is submitted by the user(2nd insert).
I have a feeling that you are testing this on a non-prod environment.
Please copy the webapp link from your test email sitting in your inbox. Open Chrome developer tools and go to network tab and enable Preserve Log.
Now paste the copied URL and hit return
You might see the tracked URL from your email being invoked twice.
We've seen this happening many times when there are security softwares installed inside your work VPN or office which first resolve the URL to ensure that it is not an invalid page and only then send the request again. If this is the case for you, it is expected and you cannot bypass it, unless your IT team starts trusting the non-prod environment emails or links.
Views
Likes
Replies
Views
Likes
Replies