# Bug - Third Party/BIA Risk - Classification settings crashes

**URL:** https://discussions.eramba.org/t/bug-third-party-bia-risk-classification-settings-crashes/3188
**Category:** Forum - Software
**Tags:** bug
**Created:** [June 15, 2023, 3:47pm UTC](https://discussions.eramba.org/t/bug-third-party-bia-risk-classification-settings-crashes/3188 "2023-06-15T15:47:58Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![fireblade](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/f/4bbf92/32.png) [@fireblade](https://discussions.eramba.org/u/fireblade)
#### Post date: [June 15, 2023, 3:47pm UTC](https://discussions.eramba.org/t/bug-third-party-bia-risk-classification-settings-crashes/3188/1 "2023-06-15T15:47:58Z")

</div>

###### **App Version**

3.20.0

###### **DB Schema Version**

20230214113829

###### Issue

when i try to setup the “Classification Types” for Third Party Risk Management instead of the expected window i get

**Error:** The requested address **‘/third-party-risk-classification-types?modalId=1&\_=1686843315816’** was not found on this server.

and for Business Impact Analysis i get

**Error:** The requested address **‘/business-continuity-classification-types?modalId=1&\_=1686843634453’** was not found on this server.

I have already setup the Classification Types for Asset Risk Management without issue

1. go to either Third Party Risk Management or Business Impact Analysis
2. open settings menu
3. click Classification Types

---

<div class="post-metadata">

### Author: ![kisero](https://discussions.eramba.org/user_avatar/discussions.eramba.org/kisero/32/2925_2.png) [@kisero](https://discussions.eramba.org/u/kisero)
#### Post date: [June 16, 2023, 9:53am UTC](https://discussions.eramba.org/t/bug-third-party-bia-risk-classification-settings-crashes/3188/2 "2023-06-16T09:53:01Z")

</div>

probably the most elegant bug report i have ever seen here. yes is a bug will be fixed on the next release. thanks.

github: [https://github.com/eramba/eramba/issues/4272](https://github.com/eramba/eramba/issues/4272)