# Handling Expected Errors
**URL:** https://connective.celigo.com/t/handling-expected-errors/3768
**Category:** Integrator.io
**Tags:** error-handling
**Created:** [March 11, 2025, 7:33pm UTC](https://connective.celigo.com/t/handling-expected-errors/3768 "2025-03-11T19:33:19Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jackharris](https://connective.celigo.com/u/jackharris)
#### Post date: [March 11, 2025, 7:33pm UTC](https://connective.celigo.com/t/handling-expected-errors/3768/1 "2025-03-11T19:33:19Z")
So, we have a flow that pulls in an X12 204 and sends it to our TMS system, Eka. Eka has a function where when a 204 is imported it will calculate the distance between the points of the load and populate that in Eka for load managagement.
However, if the load's origin point and destination point are less than a mile apart, Eka can't calculate the distance and returns a load mileage error. Knowing that this is something that is _ **going** _ to happen, there's a second import step that will set the "miles" tag to 1. This import only occurs when the returned status code isn't "200".
The reason this is a problem is when I have the load mileage error, I still get a notification about it. Since the follow-up step is already handling it I don't want to get notified about it. The notifications clog up our support software.
Any ideas?
---
### Author:  [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [March 12, 2025, 4:34am UTC](https://connective.celigo.com/t/handling-expected-errors/3768/2 "2025-03-12T04:34:45Z")
You can ignore the error with a postSubmit hook. Here is the documentation on it: [https://docs.celigo.com/hc/en-us/articles/360045807112-Ignore-specific-errors-in-a-postSubmit-hook](https://docs.celigo.com/hc/en-us/articles/360045807112-Ignore-specific-errors-in-a-postSubmit-hook)
The example is overly complicated so let me know if you need help. It would be good to see the error that you get when this does occur.