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 IDsreferenceB 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 responseIf 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 ConnectorsI 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 LOC1Fetched operations for LOC1Failed for LOC1, procurement, status 404Response: {"description":"Procurement' does not exist