worldtimeapi refresh failing

[ddcjoee]

Hello,

I have a dashboard that has been using worldtimeapi.org to get a local timestamp in Eastern Time (I believe I found that source in a thread on this forum). Anyway, it has always worked great, but over the weekend, it started giving me this error on automatic refresh:

Data source error: DataSource.Error: <ccon>The underlying connection was closed: An unexpected error occurred on a receive.. http://worldtimeapi.org/api/timezone/America/New_York. </ccon>. The exception was raised by the IDbCommand interface. Table: World Clock EST.
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: a74d68ff-510d-4a70-801c-727522169ed2
Request ID: eebb3927-3ed9-4b12-bbe0-a79241de60a6
Time: 2023-07-24 14:12:12Z

When I go to the connection details, I can try to re-establish the connection. No credentials are needed for this API, but no matter how I try to configure it, I get this error every time:

Failed to update data source credentials: The underlying connection was closed: An unexpected error occurred on a receive.Hide details
Activity ID:	6b957771-69d7-4008-970b-f939498f5c73
Request ID:	1945cca4-3667-14f0-d395-be66ac83f2e3
Status code:	400
Time:	Mon Jul 24 2023 10:24:42 GMT-0400 (Eastern Daylight Time)
Service version:	13.0.21171.58
Client version:	2307.3.14839-train
Cluster URI:	https://wabi-us-east2-redirect.analysis.windows.net/

 Anyway, does any one have any experience with something like this happening with this API or another similar one?

[rubayatyasmin]

Hi, @ddcjoee 

Here are some suggestions, you want to follow.

1. Check if the API service (worldtimeapi.org) is down.
2. Investigate if network issues, such as firewalls or proxies, are blocking your connection.
3. Look into compatibility issues with your software.
4. Consider if you're hitting the rate limit set by the API provider.
5. If none of these work, contact the API provider or consult their documentation.