Welcome to the Earthdata Forum! Here, the scientific user community and subject matter experts from NASA Distributed Active Archive Centers (DAACs), and other contributors, discuss research needs, data, and data applications.
by oceani » Thu Jan 05, 2023 4:22 pm America/New_York
Are there any issues with level 2 SST and CHL subscriptions for Aqua, Terra and VIIRS? We are not seeing data show up in the last 24 hours at the times we would usually expect the files to be available. This appears to be happening for almost all of our subscriptions, but a few example Request IDs would be: 2124, 906, 2166, 2402 and 2126. As far as we know we have not made ay changes to retrieval scripts, etc, on our end, but want to rule out issues on your side before we dig deeper here.
Addition to this post @~4:20 PM MST: I also tried to add a new subscription and received the following error message: "Something went wrong creating subscription(s).ARRAY(0x55a82a33ca38) 2023-01-05 MODIS-Terra 264"
by oceani » Fri Jan 06, 2023 12:20 pm America/New_York
At this time, according to our active subscriptions on the Data Dashboard, it looks like (with about 2-3 exceptions) our subscriptions initiated prior to 2020 are not filling in with recent data, however subscriptions created from 2020 through today are updating as expected. We have many subscriptions created prior to 2020. A few more example IDs that are not showing recent data in the Data Dashboard are: 846, 1084, 2125 and 2402. Thanks for your assistance.
We have identified the root cause of this issue. On January 4th, a bug in our subscription manager was identified and corrected. This bug allowed expired subscriptions to have data staged for them if another, non-expired subscription would have those data staged (this only affected non-extracted subscriptions). What this means is that the subscriptions in question listed in this thread were all expired. In fact, there were about 1000 affected subscriptions.
We have set a new expire date for these to be January 31st. This will cause the system to send out a notification of the impending expiration. When subscriptions are set to expire, the system sends an email to the address of the subscription owner 30 days, 15 days, 7days and 1 day prior ... so, the notice should go out on the 17th and again on the 24th and 30th if not acted upon. The email will give instructions on how to extend the subscription.
We will stage the data missed since Jan 4th for these subscriptions soon.
As for the issue reported with setting up a new subscription, that was an unrelated problem that has also been resolved.