the IA chatbot does not respond if I do not refresh the page, why?
2 Likes
I’ve checked your website and got a reply almost instantly:
Can you please check it in Incognito mode and let me know if the issue still comes up?
1 Like
Hello Helga,
Thank you for your reply.
Please try to ask something not using quick questions. The issue is when I do different questions.
Thank you.
2 Likes
Hmm, still no issues 
Does it behave like this on all your devices, including the Incognito? I’ll discuss it with the devs too!
1 Like
I tried with Incognito, desktop device with chrome and there is the same problem. I enclose you a pdf with some screenshots.
Thank you
(Attachment IAchatbot.pdf is missing)
2 Likes
Thanks a lot for the info! I’ll consult with the developers and get back to you soon 
1 Like
Thank you for waiting!
Unfortunately, none of us could replicate the issue on our end. Could you please send me a screenshot of the Developer Console after you ask a question and the the widget does not provide an answer? You can press F12 → Console to do it:
1 Like
ok
this is all the text:
js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1245 Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading
Pea @ js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1245Understand this warningAI
js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1162 As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead. At this time, google.maps.Marker is not scheduled to be discontinued, but google.maps.marker.AdvancedMarkerElement is recommended over google.maps.Marker. While google.maps.Marker will continue to receive bug fixes for any major regressions, existing bugs in google.maps.Marker will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/deprecations for additional details and https://developers.google.com/maps/documentation/javascript/advanced-markers/migration for the migration guide.
_.pm @ js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1162Understand this warningAI
js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1145 google.maps.event.addDomListener() is deprecated, use the standard
addEventListener() method instead:
https://developer.mozilla.org/docs/Web/API/EventTarget/addEventListener
The feature will continue to work and there is no plan to decommission
it.
_.Rk @ js?libraries=places&key=AIzaSyAij2uyHxecAtRVIrVQfA-zinlFdhUrsqA:1145Understand this warningAI
thank you
2 Likes
Hi there, @Villavistalago.it 
Please let me step in for Helga.
Many thanks for the screenshot!
We’ve talked to the devs and this console error isn’t related to our widget. Could you please share a video screencast of the issue with the opened Network tab?
For this, just open the Network tab (next to the Console tab) in the DevTools, send your question to the chatbot and wait a bit:
This screencast could help us find the reason for this issue 
1 Like
Ok, thank you
if I click on pending line this is the text:
Referrer Policy:
strict-origin-when-cross-origin
Response Headers
Request Headers
Request URL:
https://widget-data.service.elfsight.com/.well-known/mercure?topic=https%3A%2F%2Fwidget-data.service.elfsight.com%2Fapi%2Fai-chat%2Fassistant%2F0be18995-5125-4bc2-beba-10374995a420%2Fthread%2F0f2780eb-57c7-4a95-9ea4-4ba6a6b0b167&authorization=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJtZXJjdXJlIjp7InN1YnNjcmliZSI6WyJodHRwczovL3dpZGdldC1kYXRhLnNlcnZpY2UuZWxmc2lnaHQuY29tL2FwaS9haS1jaGF0L2Fzc2lzdGFudC8wYmUxODk5NS01MTI1LTRiYzItYmViYS0xMDM3NDk5NWE0MjAvdGhyZWFkLzBmMjc4MGViLTU3YzctNGE5NS05ZWE0LTRiYTZhNmIwYjE2NyJdfX0.wGuNRtXzZZD88yEc5WJxsHGz3h-a46IG8zrq4h9TrRph_Z29QxDQ9930Yc5iLYdmxvjIJ9LyVj1OYH_8YERcx5xmopZj5omXbAFaUufhLezPSQXeoKAL19hBUmyMkifXdmIGxqARkY5xA-VmhATrQinxobvYXoZl_Ak_8fqEXCrHpqcISag5B6ReWOU2WzmZiOdhP0uk2vWcpy4z9-lR43T5bjc4Y67qnO1kd7n6GQ4njk812jBZHSoDR4nXFcj06d5k5q6feV8OrOr3ulVhqHN2eyivaLUJAMAWYdXKGfLTD9Up2TAvcT9XXpXRQXO87HVua4iuw_Lrv2SBBg-Ut6OrbS_iUN9AQ1_rDkC3ssP1_ZtLSyEyGUX1vkrg-EeenWpk-vWsnp5sngGMoYtQI-36tvEz9Y_iTsSlLCfa1M95YFXIqVBoGnUPj5r8aUJ_BdznMmQKetpgtluwBKZzCF5a7in-PW3kMCZ0TVxcJAuI6MbPrrjOkPA5uU_k-Ch4hhEXzhh0Lws0VuQgPkX-b1XjevpU5WVAPfccf0JoW_FQksh_MNcdqnO5pODn8H2_L8-dWoe5YaMiNpAJFNFBDlAyNd-Zt7BJMaE7actMM14mHolMrgXrbgGQ2j8AlHLvx4loRMSbKnRo_ozcui7eNOqtmYrfYsXjoX1ELRj5icQ
Referrer Policy:
strict-origin-when-cross-origin
accept:
text/event-stream
accept-encoding:
gzip, deflate, br, zstd
accept-language:
it-IT,it;q=0.9
cache-control:
no-cache
connection:
keep-alive
host:
widget-data.service.elfsight.com
origin:
https://www.villavistalago.it
referer:
https://www.villavistalago.it/
sec-ch-ua:
“Not(A:Brand”;v=“99”, “Google Chrome”;v=“133”, “Chromium”;v=“133”
sec-ch-ua-mobile:
?0
sec-ch-ua-platform:
“Windows”
sec-fetch-dest:
empty
sec-fetch-mode:
cors
sec-fetch-site:
cross-site
user-agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
2 Likes
Thank you!
Now please try to open the line with the mercure?topic=.. and make a screenshot of the Event Stream tab. Please stretch this tab to the maximum width, so that all text is visible.
Here is a screencast showing how you can do this:
1 Like
Thank you so much for providing the screenshots and assisting with the issue investigation - your help is greatly appreciated
It appears that this issue is specific to your local network. I’ve gone ahead and increased your message limit until the next refresh date.
Could you please try checking the issue using a different internet connection, such as the mobile Internet on your smartphone (without WiFi)?
1 Like
Hello,
On mobile phone works properly at the moment.
Thank you.
2 Likes
Got it!
To troubleshoot the issue further, please follow these steps:
-
Restart your router
-
Open a blank page by typing about:blank in the address bar.
-
Open the Developer Console in the Dev Tools (as you did before)
-
Run this script in the Console
(async () => {
console.time('fetch');
const response = await fetch(
'https://widget-data.service.elfsight.com/.well-known/mercure'
);
console.timeEnd('fetch');
console.log('fetch status:', response.status);
console.time('sse onerror');
console.time('sse onclose');
const eventSource = new EventSource(
'https://widget-data.service.elfsight.com/.well-known/mercure'
);
eventSource.addEventListener('error', (e) => {
console.timeEnd('sse onerror');
console.error(e);
});
eventSource.addEventListener('close', (e) => {
console.timeEnd('sse onclose');
console.error(e);
});
})();
- Send the screenshot of what you see (like in the example below):
1 Like
Thanks! I’ve shared it with the devs and will get back to you a bit later 
1 Like
Hi there, @Villavistalago.it
Do I get it right that router restart didn’t resolve the issue?
If the issue still persists, please check the widget onc again on your website and through the Share Link. Please let me know how it works there.
Additional, please specify the browser you’re using and its version
1 Like
Hello the issue still persists on desktop device but not on mobile devices.
I use Google chrome and Microsoft Edge Insider
Could be the firewall of my Company the problem?
When I use another pc outside the Company it works properly.
Thank you.
2 Likes