
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 07:20 AM
Hi Folks,
One of my Asset users is getting an "HTTP status: 404" error whenever they attempt to update assets on [alm_hardware]. Despite this, the record does update for them, but this error occurs as well. Any thoughts on what may be causing this?
Thanks in advance.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 07:47 AM
Hi,
This error message is from Business Rule. Do you have any ebonding done on Asset table? I think a BR is trying to call a API. This could be response message from API.
Thank you,
Palani
Palani

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 07:47 AM
Hi,
This error message is from Business Rule. Do you have any ebonding done on Asset table? I think a BR is trying to call a API. This could be response message from API.
Thank you,
Palani
Palani

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 08:56 AM
Hi Palani, is there a way for me to debug which BR may be causing this?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 10:49 PM
Hi Jon,
Normally Asset tables will have very less Business Rules. Open the Business Rule list of that record and see whether you see a Business Rule with name similar to ebonding or integration etc. That may have code for this.
If you cant find from that add a filter and add a condition as below
script contains Looks like we ran into a problem
If the logic is moved to a script include class then the above condition will not work. In that case you may need to open the Business rule and check.
If you are still not sure then disable Business Rules one by one and see which one is causing issue.
Thank you,
Palani
Palani

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2021 01:11 PM
One way to troubleshoot is to invoke the error and look at the Outbound HTTP Logs. In there you'll see the http 404 being invoked. From there you have to code search to back your way into what code is invoke the API call. Hopefully the url being called will let you work with the right team that supports that webservice as to why an http 404 is being returned from their service.