Hey everyone, I have a quick question around mapped tasks. We have a few mapped tasks whose

mapped

field has recently started always showing up as false. Example response for one of our mapped tasks from the interactive API:

"task": [
      {      
        "id": "ad65f438-062b-4f9d-ba8e-826edce68d74",
        "name": "<task_name>",
        "mapped": false,
        "task_runs": [
          {
            "name": null,
            "created": "2021-11-11T01:08:13.326713+00:00",
            "map_index": -1,
            "version": 2
          },
          {
            "name": "<task_run_0>",
            "created": "2021-11-11T01:31:55.062178+00:00",
            "map_index": 0,
            "version": 3
          },
          {
            "name": "<task_run_1>",
            "created": "2021-11-11T01:31:55.062178+00:00",
            "map_index": 1,
            "version": 3
          }
        ]
      },

We have some logic which depends on the value of mapped. We could use

map_index != -1

in place of this I guess, but we’re trying to determine why the

mapped

field is always false despite there being mapped

task_runs

Hey @Lukas Brower, I’ll look into this.

Thanks Kevin!

I replicated. Will ask around