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
DataCite has noticed around that 38% of GBIF's requests are resulting in a 404 response. @dnoesgaard suggested I create this issue.
There is an attempt GET metadata for each around the time it is created. Sometimes, the GET requests are sent (or at least received) immediately before the POST request, so DataCite returns a 404 because the DOI doesn't exist yet. We are also seeing that GET requests are retried several times in short succession.
I'm wondering if this is intentional, and/or if it would be possible to introduce a slight delay here to reduce the errors. Here is a recent subset of our logs showing the request pattern: extract-2023-11-08T21_55_39.934Z.csv
The text was updated successfully, but these errors were encountered:
DataCite has noticed around that 38% of GBIF's requests are resulting in a 404 response. @dnoesgaard suggested I create this issue.
There is an attempt GET metadata for each around the time it is created. Sometimes, the GET requests are sent (or at least received) immediately before the POST request, so DataCite returns a 404 because the DOI doesn't exist yet. We are also seeing that GET requests are retried several times in short succession.
I'm wondering if this is intentional, and/or if it would be possible to introduce a slight delay here to reduce the errors. Here is a recent subset of our logs showing the request pattern: extract-2023-11-08T21_55_39.934Z.csv
The text was updated successfully, but these errors were encountered: