# Temporarily wrong retrievals of C3S seasonal forecast data from NCEP - Issue now resolved

**URL:** <https://forum.ecmwf.int/t/temporarily-wrong-retrievals-of-c3s-seasonal-forecast-data-from-ncep-issue-now-resolved/1578>\
**Category:** C3S - Announcements\
**Tags:** seasonal\_forecast, c3s\
**Created:** [26 October 2020 10:01 UTC](https://forum.ecmwf.int/t/temporarily-wrong-retrievals-of-c3s-seasonal-forecast-data-from-ncep-issue-now-resolved/1578 "2020-10-26T10:01:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anabelle](https://forum.ecmwf.int/user_avatar/forum.ecmwf.int/anabelle/32/360_2.png) [@Anabelle](https://forum.ecmwf.int/u/Anabelle)\
**Post date:** [26 October 2020 10:01 UTC](https://forum.ecmwf.int/t/temporarily-wrong-retrievals-of-c3s-seasonal-forecast-data-from-ncep-issue-now-resolved/1578/1 "2020-10-26T10:01:15Z")

</div>

An issue in the CDS infrastructure affecting some seasonal forecast retrievals has been identified. It will be tracked as error (E7b) in the [seasonal forecast known issues](https://confluence.ecmwf.int/display/CKB/C3S+Seasonal+Forecast+known+issues) page.

This error prevents users from getting all available members from CFSv2-v20110310 ( **NCEP CFSv2** ) data.&nbsp;This issue affects retrievals done **after the release** of the October 2020 forecast, which happened at 12UTC **on the 13th of October 2020.**

It affects all data available in the **high-frequency (daily/subdaily)** datasets:

- [seasonal-original-single-levels](https://cds.climate.copernicus.eu/cdsapp#!/dataset/seasonal-original-single-levels)
- [seasonal-original-pressure-levels](https://cds.climate.copernicus.eu/cdsapp#!/dataset/seasonal-original-pressure-levels)

**Members with start time at 06h,12h and 18h are not being retrieved** from the archive by the CDS and just members with start time at 00h are returned.

This is currently under investigation and it will be announced here once the issue has been resolved.

Update 27/October/2020

The issue described above has been&nbsp; **solved** &nbsp; **at 16:15UTC on the 26/October/2020**. All retrievals should be correct now, and just those retrievals performed between 13/Oct/2020 at 12UTC and 26/Oct/2020 at 16:15UTC have been affected.