Input filter that looks for 404 Error from previous step

Daniel Lougheed

• December 16, 2021 19:32

Is it possible to use an input or output filter via error code or status code? I am looking to only go to a final step if the record is missing or not found. returning a 404 

1

• 

  Kate Larson Senior UX Researcher Community moderator

  • December 20, 2021 15:11

  Hi Daniel Lougheed -
  It looks like you're working with our Support team on this. If you get a chance to post an update to the community once it's resolved in case someone else has this question, that would be great.

  Thanks,

  Kate

  0
• 

  CJ Sell

  • April 21, 2023 20:32

  

  Hello! Have there been any updates on this case?

  Thanks!

  0
• 

  Anitha Abraham Principal Technical Writer

  • May 02, 2023 10:24

  

  CJ Sell, Support provided guidance after analyzing the specific customer use case. Could you please explain your use case so that we can help you?

  Meanwhile, here are two references that might be helpful:

  • Throwing an error using the Post Submit hook
  • Ignore specific errors in a Post Submit hook

  Thanks!

  0
• 

  CJ Sell

  • May 03, 2023 17:41

  

  Anitha Abraham, Thank you for the response on this! 

  We are performing a GET request to an HTTPS endpoint to check if a record is missing in the endpoint's system. If the record is missing, however, the endpoint throws a 404 error code (with a message stating why the 404 code) instead of a simple "Missing record" message. This in turn causes the Celigo flow to error at this stage. We would like for the 404 error message to be ignored and ultimately passed to the next step in the flow.

  Thank you!

  CJ

  0
• 

  Tyler Lamparter Senior Solutions Consultant

  • May 05, 2023 14:32

  

  

  

  

  

  CJ Sell you can use this functionality:
  

  You also would need to response map the errors or status code so you could filter or branch on it later.

  

  0

Please sign in to leave a comment.