HLS STAC "Oops!" error occurring every day around 2 pm pacific time.

[matushodul]

We noticed that the HLS “Oops!” error* seems to occur at roughly the same time every day, so we created a script which checks the status of HLS throughout the day. Indeed, the oops error occurs every day around 2 pm pacific time, and lasts for a couple hours, after which it resolves itself. This would match observations from @rbrassfield of the error occurring at 3 pm mountain time, and from @matthew_cox_omnia at 4:30 pm central time.

There are other periods of oops error during the day as well, but these are shorter and don’t seem to follow a specific pattern.

* full error is: pystac_client.exceptions.APIError "Oops! Something has gone wrong. We have been alerted and are working to resolve the problem. Please try your request again later."

import sys, os
from pystac_client import Client
import time

def checkHLS():
try: # run a large HLS Query:
url = r'https://cmr.earthdata.nasa.gov/stac/LPCLOUD'
cat = Client.open(url)

geom = {
'type': 'Polygon',
'coordinates': [[[-121.48363199406296, 50.58244919445883], # for an ROI near Cache Creek, BC.
[-121.44546042608697, 50.58244919445883], # normally these coords are derived from a .shp
[-121.44546042608697, 50.700797792110535], # but I didn't include that part in this demo.
[-121.48363199406296, 50.700797792110535],
[-121.48363199406296, 50.58244919445883]]]
}

params = {
'intersects': geom,
'collections': ['HLSL30.v2.0'],
'datetime': '2018-01-01/2024-01-01'
}

search = cat.search(**params)
items = search.item_collection()

# If it works, return a status code of 1
return 1, None, None

except: # if it doesn't work, return a status code of 0 and the error message
the_type, the_value, the_traceback = sys.exc_info() # https://stackoverflow.com/a/19406123

return 0, the_type, the_value

[LP DAACx - dgolon]

Hi @matushodul Please look for your issue here: https://github.com/nasa/cmr-stac/issues, if you do not see any related issues posted please post what you mentioned there. Thanks -- Danielle

[aaleman]

We're looking into it, but so far, it doesn't appear to be a CMR-STAC issue but rather something happening upstream with CMR. Status updates on the issue can be tracked in the repo: https://github.com/nasa/cmr-stac/issues/366

[aaleman]

Also want to share an update regarding the communication of changes and releases, as well as reporting and tracking issues for CMR-STAC...

• Release notes are now available in the CMR-STAC GitHub repo: https://github.com/nasa/cmr-stac/releases. The production release cadence for CMR-STAC is typically every two weeks on Wednesday, and release notes will be posted 2 weeks ahead of scheduled release dates. The next scheduled release to production is 11/20/2024.

• The CMR-STAC GitHub repo will also be The Place for reporting and tracking the status of issues and feature requests going forward. You can check the current list of open issues here: https://github.com/nasa/cmr-stac/issues.

I'm hopeful this streamlined approach to communications will make it easier for everyone to report and track the status of issues, fixes, and new feature requests for CMR-STAC. Please reach out if you have questions or concerns.