Handling HTTP 404 errors in Enhanced Data Connectors

I’m currently working with TX Enhanced Data Connectors and have noticed that there doesn’t seem to be a built‑in way to handle HTTP 404 errors. 

Heres is a senario:
I have en endpoint which is:

/api/{referenceA}/{referenceB}

referenceA are office-location IDs
referenceB are values like [sales, procurement, operations]

I can do this either by GET, this way:
 

or, by POST, this way:
 

{
  "referenceA": {officeLocations},
  "controlCurves": [
    "sales", "procurement", "operations"
  ]
}

If an office location (referenceA) has all three departments (referenceB), i get a response
If an office location (referenceA) has one or more departents (eferenceB) missing, the extraction stops.

I have also tried it with a GET method in TX Enhanced Connectors

I dont want the extraction to stop, i want it to skip and go to next value. Something like this (log from a python script):
 

Fetched sales for LOC1
Fetched operations for LOC1
Failed for LOC1, procurement, status 404
Response: {"description":"Procurement' does not exist for location 'LOC1'"}
Fetched sales for LOC2
Fetched operations for LOC2
Fetched procurment for LOC2
Fetched sales for LOC3
Fetched operations for LOC3
Fetched procurment for LOC3
Fetched sales for LOC4
Failed for LOC4, operations, status 404
Response: {"description":"Operations' does not exist for location 'LOC4'"}
Fetched procurment for LOC4

In python, the code just moves to the next location and creats a table.

Does TimeXtender already provide any solution for handling 404 errors directly within the Enhanced Data Connectors?

If not, would it be appropriate to submit this as a feature request?