HTTP 500 Internal Server Error: KeyError('mapzedn-dem')

Dear openEO Platform Team,
I am getting this error for the process graph attached below.
When using vitos dev backend it works.

HTTP 500 Internal Server Error.
ā€¢ SERVER-ERROR: Server error: OpenEoApiError("[500] Internal: Server error: KeyError('mapzen-dem') (ref: r-52bd9f0b4de643ceaa55ce569dac0c63)")

PG (ID: vito-j-ae2d81fa8f5148d2a91473205ec2f9f9): (tested also with Terrascope S2 TOC collection and an spatial extent used at lps that used to work)

{
  "process_graph": {
    "load_collection_JKRMV6135N": {
      "arguments": {
        "bands": [
          "B04",
          "B08"
        ],
        "id": "SENTINEL2_L2A",
        "spatial_extent": {
          "east": 5.634381,
          "north": 51.982536,
          "south": 51.975763,
          "west": 5.621606
        },
        "temporal_extent": [
          "2018-01-01",
          "2019-01-01"
        ]
      },
      "process_id": "load_collection"
    },
    "reduce_dimension_BQERB8082E": {
      "arguments": {
        "data": {
          "from_node": "load_collection_JKRMV6135N"
        },
        "dimension": "bands",
        "reducer": {
          "process_graph": {
            "add_PNMNM2194U": {
              "arguments": {
                "x": {
                  "from_node": "array_element_VMPQS0739R"
                },
                "y": {
                  "from_node": "array_element_GNUOC6021D"
                }
              },
              "process_id": "add"
            },
            "array_element_GNUOC6021D": {
              "arguments": {
                "data": {
                  "from_parameter": "data"
                },
                "index": 0,
                "return_nodata": false
              },
              "process_id": "array_element"
            },
            "array_element_VMPQS0739R": {
              "arguments": {
                "data": {
                  "from_parameter": "data"
                },
                "index": 1,
                "return_nodata": false
              },
              "process_id": "array_element"
            },
            "divide_JHWWW8316P": {
              "arguments": {
                "x": {
                  "from_node": "subtract_IPBYJ0289A"
                },
                "y": {
                  "from_node": "add_PNMNM2194U"
                }
              },
              "process_id": "divide",
              "result": true
            },
            "subtract_IPBYJ0289A": {
              "arguments": {
                "x": {
                  "from_node": "array_element_VMPQS0739R"
                },
                "y": {
                  "from_node": "array_element_GNUOC6021D"
                }
              },
              "process_id": "subtract"
            }
          }
        }
      },
      "process_id": "reduce_dimension"
    },
    "reduce_dimension_VWQKE9897S": {
      "arguments": {
        "data": {
          "from_node": "reduce_dimension_BQERB8082E"
        },
        "dimension": "t",
        "reducer": {
          "process_graph": {
            "mean_IENUS7850C": {
              "arguments": {
                "data": {
                  "from_parameter": "data"
                },
                "ignore_nodata": true
              },
              "process_id": "mean",
              "result": true
            }
          }
        }
      },
      "process_id": "reduce_dimension"
    },
    "save_result_KXFDA3650Q": {
      "arguments": {
        "data": {
          "from_node": "reduce_dimension_VWQKE9897S"
        },
        "format": "GTiff",
        "options": {}
      },
      "process_id": "save_result",
      "result": true
    }
  }
}
1 Like

Thanks for reporting!
Apparently a change of layer id to uppercase on sentinelhub caused this.
Iā€™m redeploying the production backend to solve this.

Hi @jeroen.dries,
thanks for fixing this directly. I can confirm that it works now.
Thanks, all the best,
Peter