Suppress API 404 error from appearing in BizTalk console
I have a BizTalk app that calls an API from one of our suppliers. The orchestration receives a list of users and a list of subscriptions for that user. It then goes on to check whether the user exists, and if so, it posts them into the user table. It then goes on to post or update the subscription records, within another table.
The issue is that the call I have to make to the API to see whether a user exists returns a 404 error if they don't. I can account for this within the orchestration using a catch exception, so that if we receive a 404 error saying the user doesn't exist, it then creates a record for them and continues to create or update the subscriptions. However, by this point it's already been through the send port, and therefore creates an error in the console, even though this is a false error as the user not existing is to be expected in most cases.
Is there a way I can somehow suppress this particular error message, so it doesn't appear in the console?
I have checked with the supplier and there is currently no call I can make for the 'does user exist?' check that won't return a 404 error if they don't. The only other call I could make is to try and insert the user without checking whether they exist, in which case it returns a 404 error if they already do, which leaves me with the same issue. I don't unfortunately know anything about rerouting errors in BizTalk, but I'm hoping there's a way to tell BizTalk to ignore an error if the response contains 'user doesn't exist'.
Even if I can just reroute this error to a file somewhere, and have it not appear as an error in the console, this would suffice.
I'm assuming you are talking about suspended messages.
Simply enable Routing for Failed messages on the port, and either have a port or an Orchestration subscribe to them with a filter like ErrorReport.FailureCode Exists, and have that send port either write to them a file location that gets purged, or a custom adapter that just throws the message away.
- How to handle an Azure Function rerunning when using message queue binding?
- Custom 404 error page not working with Struts 2
- Either and inner Maybe error handling
- Handle 503 error when making jobs.insert call
- What is the difference between adding the `?` operator and not adding it in this call?
- Xcode is damaged and refuse to run the code
- Error handling in C code
- get stack trace on tryCatch'ed error in R
- Getting error "CodeIgniter\Cache\Exceptions\CacheException Cache unable to write to ... " for a new Codeigniter 4 project
- How to implement a (derived) Exception type in Julia?
- What is the most concise way to source a file (only if it exists) in Bash?
- How to convert between MyError type and anyhow::Error, and also handle the conversion conflict with std::error::Error?
- Electron - Is there a way to run code after throwing an error?
- What's the type of React Query's Error and how to handle different cases?
- NASM Calculator - Won't print the result
- Proper way to throw errors on ExpressJS and consume them on Typescript client?
- How can I test and handle a #Func! error from within a query?
- Numpy error: underflow encountered in exp
- Powershell -ErrorAction SilentlyContinue not adding error to $Error variable
- Access the context variable without passing it in from a command in a lower level function in a Discord bot?
- Getting a typeError error in django project
- Upgrading from PHP7.4 => PHP8, is it possible to ignore certain errors
- A property or indexer may not be passed as an out or ref parameter
- Uncaught Error: useNatureRecord must be used within a NatureRecordProvider in React Native TypeScript app
- MsgBox for error handling in a VBA UDF called from cells in Excel?
- Adding custom 404 error page in ASP.NET Core 6 MVC project integrated with Identity
- How to output the 'Underlying SQLException' from Azure Databricks instead of the generic exception message?
- Should I expect "device lost" conditions as normal under Vulkan?
- ECGraph not working on device, but works on simulator
- Design pattern for handling a lot of error codes