Closed bossie closed 2 months ago
For reference, and for reproducing purposes, the process graph in question:
{
"process_graph": {
"loadcollection1": {
"process_id": "load_collection",
"arguments": {
"bands": [
"B02"
],
"id": "SENTINEL2_L2A",
"spatial_extent": null,
"temporal_extent": null
}
},
"filterbbox1": {
"process_id": "filter_bbox",
"arguments": {
"data": {
"from_node": "loadcollection1"
},
"extent": {
"west": 11.279182434082033,
"east": 11.406898498535158,
"north": 46.522729291844286,
"south": 46.464349400461145,
"crs": 32632
}
}
},
"filtertemporal1": {
"process_id": "filter_temporal",
"arguments": {
"data": {
"from_node": "filterbbox1"
},
"extent": [
"2018-06-06",
"2020-10-22"
]
}
},
"saveresult1": {
"process_id": "save_result",
"arguments": {
"data": {
"from_node": "filtertemporal1"
},
"format": "GTiff",
"options": {}
},
"result": true
}
}
}
committed something for the relevant error handler, which was not looking for 'ErrorMessage'.
Fix should be live, but hard to reproduce because we also have now a solution in place that avoids this error.
A CDSE catalog request failed but the ERROR message nor its stack trace contain any details with regards to the root cause, making analysis unnecessarily difficult:
There is an INFO log earlier that at least tells us that it's a 504 error:
The response to that request was actually this: