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
Severity: ERROR Cause: It was not possible to connect to the specified fetching URL. Effect: The feed version is discarded. The last successfully fetched feed version, if available, is used. Possible Resolutions: Verify that the URL provided for fetching is correct. First Seen: 2022-11-17 13:09:05 UTC Last Seen: 2022-11-17 13:09:05 UTC
Fetches affected: 1 / 1417 (0%)
This has only happened once in the past eleven days since feed testing on Google Maps started. Does not seem to be a persisting problem since it has only shown up once. The suggest resolution (verify the URL provided for fetching is correct) should be disregarded in this case since we know the URL is correct and has been working for any subsequent fetch attempts. I also confirmed that the link is correct through the e-mail I sent to Google Maps. Submitting this for the purpose of documentation on the possible issues that we could face.
If I read this correctly, 1 out of 1417 fetches failed. that's 0.07%. This could be caused for instance by a server deployment, which could lead to a fetch timing out, or the URL temporarily being unavailable.
Please provide direct links to issues wherever possible so that we can check for additional details that may be lurking somewhere (e.g. HTTP response code in this case).
Severity: ERROR
Cause: It was not possible to connect to the specified fetching URL.
Effect: The feed version is discarded. The last successfully fetched feed version, if available, is used.
Possible Resolutions: Verify that the URL provided for fetching is correct.
First Seen: 2022-11-17 13:09:05 UTC
Last Seen: 2022-11-17 13:09:05 UTC
Fetches affected: 1 / 1417 (0%)
This has only happened once in the past eleven days since feed testing on Google Maps started. Does not seem to be a persisting problem since it has only shown up once. The suggest resolution (verify the URL provided for fetching is correct) should be disregarded in this case since we know the URL is correct and has been working for any subsequent fetch attempts. I also confirmed that the link is correct through the e-mail I sent to Google Maps. Submitting this for the purpose of documentation on the possible issues that we could face.
LINK
The text was updated successfully, but these errors were encountered: