When a 404 isn't really

David Gollom Strategic Partner

• October 01, 2020 03:40

Hi Everyone,

Looking for tips/tricks here.

I'm dealing with an REST API that sends recently updated orders. When there are orders to be sent, we receive an array of data and all is well. 

The problem is when we send a perfectly valid GET to the same end point and there's no data. The API  responds with a 404 Status and Not Found.   

 "errors": [
    {
      "code": 404,
      "message": "Not Found",
      "source": "application"
    }

This response results in a Failed error message in the IIO dashboard for the job.  Very annoying because it's not really an error.  The API developer said they won't change it.

Is there a way I can use a script or maybe the Non Standard Response setting to handle these 404 errors better?  

Maybe the new error handling features will let me deal with this?  

 

Thanks!!! 

 

 

 

0

• 

  viliandy leonardo Product Management Director

  • October 01, 2020 16:37

  David Gollom

  In that case, you may consider using a script to ignore this specific error - though the error message is really generic and you should evaluate other errors from the same endpoint to ensure you don't get a false positive treatment for a legitimate error. Here is a kb article with sample code.

  The new error handling feature will not deal with this use case, but we have in the backlog a feature to let users configure errors to ignore so that users don't have to build a script.

  Thanks 

   

  0
• 

  Matt Graney Chief Product Officer

  • October 01, 2020 16:41

  

  

  

  (deleted my earlier comment because I realized that this is a problem on the initial export in the flow, whereas response mappings are used downstream of that.)

  0
• 

  David Gollom Strategic Partner

  • October 01, 2020 16:43

  

  

  

  

  

  Thanks for the help.  This is an Export so the hook seems to be the Pre Save Page. It sounds like we're stuck. 

  0
• 

  viliandy leonardo Product Management Director

  • October 01, 2020 21:08

  David Gollom

  Thank your for pointing out that this is an export step.

  This is not a common integration scenario because of the non-standard response returned by that endpoint. There is a potential solution but it requires a bit set-up. The idea is to replace your existing export with a new export step that calls Celigo My API endpoint. You then delegate to My API  to invoke the application endpoint and then use the script inside My API to handle the error.

  Here is what the set-up looks like: 

  1. Start  with your existing flow: Export A - then do Import B

  2. Create a new export for Application type of "integrator.io". Proceed to create "integration.io" connection by supplying the Celigo API tokens. Call this Export A1

  3. Replace the existing export Step A with A1. So your flow is now Export A1 - then import B

  4. Create a My API resource and its respective custom script to invoke export A step url (you can find this url in the Advanced section of the export A step). You also may want to check out this kb on how to create an equivalent virtual export A so that your script can pass the parameter.

  5. Implement the error handling logic inside the My API custom script.

  • When the export A return 404, then script returns empty array of record to the export A1.
  • Otherwise, return the array record. 

  6. Configure export Step A1 to invoke a My API url which in turn will run your custom script. 

  Please let us know how this option works out for you.

  Thanks

  0

Please sign in to leave a comment.