Forum Discussion
Gateway does not connect to web
- 1 year ago
Hi FotFly,
Thank you for the update, and no problem, we appreciate your response!
It's notable that the test connection failed but the actual refresh succeeded. This can happen due to temporary DNS or connectivity issues during testing, or because there are differences between test connection validation and actual data refresh, especially when using web connectors with Anonymous authentication.
In these cases, skipping the test connection is an acceptable workaround if you're sure the data source and gateway are set up correctly.
Consider using raw URLs or APIs: If you are currently utilizing Web.Page, it may be beneficial to switch to structured data endpoints such as JSON or CSV APIs.
If the issue continues or you require enhanced control, transitioning to the standard (enterprise) gateway can provide improved support for complex data sources.
Also, please continue to monitor the gateway logs for any runtime errors, particularly if refresh failures reoccur.
Thank you.
Hi FotFly
If the same exact connections from the same dataset used to work and it now fails then try to update the gateway.
Hi aj1973,
Thank you for your answer. I have tried updating it multiple times now and the issue persists. From the gateway export log I was not able to figure out what is the issue when trying to connect.
- aj19731 year agoCommunity Champion
Yes the message you receive can be incomprehensive. Can I see it tho?
Have you changed anything lately in the dataset? Have you changed connections in the Dataset in your desktop?...