Hi ​@Adina, I’ve had a brief look at the information in your Attachment and it looks like this is something you need to formally report to IFS by logging a Support Case. Then a Support Team member will accept the Case and investigate the issue as being a Suspected Software issue and provide you a fix/resolution steps.

Note: I’ve also done a Knowledge check on this and found that a correction was provided to fix the same error Message (The Test scenario is a bit different but the error is exactly the same), but that correction is currently available for Cloud versions only (IFS Cloud 23R2 upwards). Anyway, once you formally report this as a Support Case, IFS Support will evaluate this further and see if a tailor-made correction can be provided for IFSAPP10 also.