--- title: Criticality, RTO, RPO, and special value issues description: Grouped troubleshooting page for B_06.01/B_07.01 issues on criticality assessment, dates, RTO/RPO, impact levels, and placeholder values, rewritten to stay within REG/UI-supported rules. --- [Skip to content](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#main-content) English Show submenu for translations [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg)](https://support.copla.com/?hsLang=en) Open main navigation Close main navigation - English Show submenu for translations - [Contact us](mailto:support@copla.com) [Contact us](mailto:support@copla.com) How can we help you? - There are no suggestions because the search field is empty. 1. [Copla Help Center](https://support.copla.com/?hsLang=en) 2. [Copla Registry](https://support.copla.com/copla-registry?hsLang=en) 3. [Troubleshooting](https://support.copla.com/copla-registry?hsLang=en#troubleshooting) # Criticality, RTO, RPO, and special value issues ## Grouped troubleshooting page for B\_06.01/B\_07.01 issues on criticality assessment, dates, RTO/RPO, impact levels, and placeholder values, rewritten to stay within REG/UI-supported rules. #### What this issue group covers These issues sit in the same part of the register and are often checked together: `Functions`for functions identification and, where relevant, `ICT service assessments` for assessments of ICT services supporting a critical or important function. The fields do not use the same rule, so each one needs to be checked against its own instruction. This page helps you check the allowed values for **`Criticality or importance assessment`**, **`Date of the last assessment`** of criticality or importance, `Recovery time objective` of the function, `Recovery point objective` of the function, `Impact of discontinuing` the function, and the placeholder values `9999-12-31` and `0`. #### Issues covered on this page - [My record is failing because no criticality assessment was performed](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#no-ciriticality-assessment) - [My criticality assessment date is being flagged](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#criticality-date-flagged) - [My RTO or RPO value is being rejected](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#rto-rpo-rejected) - [I do not know what to enter for RTO or RPO](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#how-enter-rto-rpo) - [I am not sure how to enter this special value](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#how-to-special-value) - [I am not sure which impact level to choose](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#which-impact-level) --- ### My record is failing because no criticality assessment was performed #### What this usually means The `Functions` field **`Criticality or importance assessment`** is blank, or the same `Functions` entry does not use the allowed reporting for an unperformed assessment. “Assessment not performed” is an allowed option. The issue is usually that it was not reported explicitly, or that the related date does not match it. #### What to check and how to fix it **Check the `Functions` field `Criticality or importance assessment`.** If it is blank, enter one of the allowed values: `Yes`, `No`, or `Assessment not performed`. **Check whether `Assessment not performed` is the correct state for this function.** If it is, keep that value and set **`Date of the last assessment`** of criticality or importance to `9999-12-31`. **Check whether the function has already been assessed.** If it has, replace `Assessment not performed` with `Yes` or `No` and enter the real date of the last assessment. **Check the same `Functions` entry for `Recovery time objective` of the function, `Recovery point objective` of the function, and `Impact of discontinuing` the function.** If any of those are blank or use the wrong placeholder, correct each field using its own rule. **Check related `ICT service assessments` entries only after the `Functions` function entry is correct.** If an ICT service supports this function, review the ICT service assessment fields separately. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) --- ### My criticality assessment date is being flagged #### What this usually means The value in `Date of the last assessment` of criticality or importance does not fit the reported value in `Criticality or importance assessment`, or the date format is wrong. #### What to check and how to fix it **Check the `Functions` field** `Date of the last assessment` **of criticality or importance against `Criticality or importance assessment`.** These two fields need to be reported together. If **`Criticality or importance assessment`** is `Assessment not performed`, enter `9999-12-31` in Date of the last assessment of criticality or importance. If **`Criticality or importance assessment`** is `Yes` or `No`, replace `9999-12-31` with the real date of the last assessment. **Check the date format.** If you are reporting a real date, use `yyyy-mm-dd`. **Check the field by name if your field codes look shifted.** The Official Journal version of `Functions` has a numbering error, so confirm the field using the field name, not only the published code. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) --- ### My RTO or RPO value is being rejected #### What this usually means The value in `Recovery time objective` of the function or `Recovery point objective` of the function is not reported as a natural number of hours, or the special values have been used in the wrong way. #### What to check and how to fix it **Check `Recovery time objective` of the function and `Recovery point objective` of the function in `Functions`.** If either value is not a whole number of hours, convert it before reporting it. **Check whether the objective is less than 1 hour.** If it is, report `1`. **Check whether the objective is not defined.** If it is not defined, report `0`. **Check that you have not used text, decimals, minutes, or `9999-12-31` in either recovery field.** Replace those with the correct numeric value. **Where the same ICT service supports several functions, check the related ICT service assessment separately.** The service should comply with the shortest RTO and RPO of the functions it supports. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) --- ### I do not know what to enter for RTO or RPO #### What this usually means You do not yet have a value ready to report for `Recovery time objective` of the function or `Recovery point objective` of the function, or you need to convert an internal target into the register format. #### What to check and how to fix it **Check whether the function already has an internal recovery target.** If it does, convert that target into hours and enter it as a natural number. **Check whether the recovery target is less than 1 hour.** If it is, enter `1`. **Check whether the recovery target is not defined.** If it is not defined, enter `0`. **Check that you are completing the `Functions` function entry.** In the register, RTO and RPO are reported for functions. If the same ICT service supports several functions, keep the function values separate in `Functions` and then cross-check the related ICT service assessment only if needed. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) --- ### I am not sure how to enter this special value #### What this usually means The special value itself is allowed, but only in specific fields and for specific cases. The problem is usually that the value has been used in the wrong field. #### What to check and how to fix it **Check which field you are completing.** `9999-12-31` and `0` are not interchangeable. Use `9999-12-31` only in `Date of the last assessment` of criticality or importance where `Criticality or importance assessment` is `Assessment not performed`. Use `0` only in `Recovery time objective` of the function or `Recovery point objective` of the function where the objective is not defined. If the real recovery target is less than 1 hour, enter `1`, not `0`. If you used `9999-12-31` or `0` in `Criticality or importance assessment`, `Impact of discontinuing` the function, or any `ICT service assessments` impact field, replace it with one of the allowed closed-list options for that field. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) --- ### I am not sure which impact level to choose #### What this usually means The selected impact value does not follow the allowed closed-list options, does not match the entity’s internal definitions in `Definitions`, or the function impact and ICT service impact have been mixed. #### What to check and how to fix it **Check whether you are filling `Impact of discontinuing the function` or `Impact of discontinuing the ICT services`.** These are different assessments. If you used the service impact to complete the function field, or the reverse, correct the relevant entry. **Check the allowed options for the relevant field.** Use `Low`, `Medium`, `High`, or `Assessment not performed`. **Check your internal definitions for `Low`, `Medium`, and `High`.** If the selected option does not follow those internal definitions, replace it with the correct one. **Check whether an assessment has been performed for that field.** If it has not, use `Assessment not performed` instead of selecting `Low`, `Medium`, or `High`. **Check the same entry again after correcting the impact field.** For `Functions`, review **`Criticality or importance assessment`**, `Date of the last assessment` of criticality or importance, `Recovery time objective` of the function, and `Recovery point objective` of the function. For `ICT service assessments`, review only the ICT service assessment fields in that template. [Back to top](https://support.copla.com/criticality-rto-rpo-and-special-value-issues#top) #### What to do next After you correct the relevant `Functions` function entry and, where relevant, the related `ICT service assessments` ICT service entry, save the record and run validation again. If a field is still being flagged, check whether the issue is the reported value, the date format, or the use of a placeholder in the wrong field. - [Core Guardian](https://support.copla.com/core-guardian?hsLang=en#main-content) - [General Instructions](https://support.copla.com/core-guardian?hsLang=en#general-instructions) - [Additional Information](https://support.copla.com/core-guardian?hsLang=en#additional-information) - [Demo Platform](https://support.copla.com/core-guardian?hsLang=en#demo-platform) - [Integration Setups](https://support.copla.com/core-guardian?hsLang=en#integration-setups) - [Copla Registry](https://support.copla.com/copla-registry?hsLang=en#main-content) - [Getting started](https://support.copla.com/copla-registry?hsLang=en#getting-started) - [Completing the Register](https://support.copla.com/copla-registry?hsLang=en#completing-the-register) - [Troubleshooting](https://support.copla.com/copla-registry?hsLang=en#troubleshooting) - [FAQ](https://support.copla.com/copla-registry?hsLang=en#faq) - [VendrIQ](https://support.copla.com/vendriq?hsLang=en#main-content) - [Trial](https://support.copla.com/vendriq?hsLang=en#trial) - [Overview](https://support.copla.com/vendriq?hsLang=en#overview) [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg "main-black-pinkglasses")](http://copla.com) [support@copla.com](mailto:support@copla.com) [mailto:support@copla.com](mailto:support@copla.com) Copyright © 2026, Copla