You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An api call took just over 30 seconds, and I think it shouldnt take that long
For example http://api.nowcasting.io/v0/solar/GB/gsp/0/forecast?start_datetime_utc=2025-02-13T00:30:00&end_datetime_utc=2025-02-18T00:00:00&creation_limit_utc=2025-02-12T00:00:00
Context
there are some failing en points hits, due to checking data that is not there. But dont think these should matter
Something to do with this message Waited 30 seconds but response not in cache. Setting this route as not running, and continuing
Possible Implementation
check these enpoints and see what is happening.
The text was updated successfully, but these errors were encountered:
Detailed Description
An api call took just over 30 seconds, and I think it shouldnt take that long
For example
http://api.nowcasting.io/v0/solar/GB/gsp/0/forecast?start_datetime_utc=2025-02-13T00:30:00&end_datetime_utc=2025-02-18T00:00:00&creation_limit_utc=2025-02-12T00:00:00
Context
Waited 30 seconds but response not in cache. Setting this route as not running, and continuing
Possible Implementation
The text was updated successfully, but these errors were encountered: