-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Urgent] Dataset Tables Erroring #233
Comments
Morning, can I just check the versioning you're looking for, our latest published version appears to be v4.0.246, not v4.0.269 |
Morning Steve, we've pulled v4.0.269 from the following: https://data.api.trade.gov.uk/v1/datasets/uk-tariff-2021-01-01/versions?format=json |
Thanks, we're going to look into this now for you |
Bril, thanks for confirming |
Hi, v4.0.269 now appears to be loading data correctly, we think there was a pipeline delay somewhere which we're still in the process of debugging. |
Thanks Steve, can confirm that version's looking good this side. Will leave this open and await to hear on the ongoing solution. |
Morning Steve, just to make you aware we've seen the same issue as above occur on v4.0.275 today. |
Our integration with the data API has been reporting errors this morning, as dataset tables under the latest version (v4.0.269) are throwing an error on attempting to access them.
For example, attempting to pull a CSV of commodity measures via https://data.api.trade.gov.uk/v1/datasets/uk-tariff-2021-01-01/versions/v4.0.269/tables/measures-on-declarable-commodities/data?format=csv results in the following:
<?xml version="1.0" encoding="UTF-8"?> <Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>uk-tariff-2021-01-01/v4.0.269/tables/measures-on-declarable-commodities/data.csv</Key><RequestId>Y5H3WEKY1GBDE0C7</RequestId><HostId>ypmd45sGXEhHwI4PFd8shgUg5shAK4o9UnjfZfv5kUxbFrL+nI/iQAf6eA2FDNpJcHV+nOZifjc=</HostId></Error>
The prior version seems to be working fine and I can fetch results for it.
The text was updated successfully, but these errors were encountered: