# WDI and error from frequency code

**URL:** <https://dbnomics.discourse.group/t/wdi-and-error-from-frequency-code/610>\
**Category:** Uncategorized\
**Created:** [July 5, 2022, 1:53pm UTC](https://dbnomics.discourse.group/t/wdi-and-error-from-frequency-code/610 "2022-07-05T13:53:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cbenz](https://yyz2.discourse-cdn.com/free1/user_avatar/dbnomics.discourse.group/cbenz/32/33_2.png) [@cbenz](https://dbnomics.discourse.group/u/cbenz)\
**Post date:** [July 5, 2022, 2:41pm UTC](https://dbnomics.discourse.group/t/wdi-and-error-from-frequency-code/610/2 "2022-07-05T14:41:51Z")

</div>

There was an update of the DBnomics fetcher for the World Bank. This impacted all the datasets of WB, but in the particular case you mention, it seems to be a bug.

I’m going to investigate. Thank you for reaching out.

See also: [EMBI data availability - #10 by cbenz](https://dbnomics.discourse.group/t/embi-data-availability/584/10)

---

_[View the full topic](https://dbnomics.discourse.group/t/wdi-and-error-from-frequency-code/610)._