Trust score is calculated based on the settings.

Manually updated means, did you perform direct update in the database?

If you execute revalidate for that particular record then it will recalculate trust and updates accordingly.

You can check below KB to

Run the Batch revalidate API for a subset of records where the records count is huge in number

Support

You should avoid using direct SQL update as the dependent tables doesn't get updated with the relevant values and it could create an issue during BVT calculation.

Did you made any changes to the validation rules recently because of which the data needs to be revalidated? Please note that revalidate job only needs to be executed when you are modifying the validation rules since the last load. If there is just data change, you do not need to execute the revalidate job at all.

In such a scenario, you just need to update the data via a regular Load Job or SIF API for it to reflect the correct trust values.

If you are facing performance issues with revalidate - you may want to tweak the multithreaded batch properties for performance improvement  -

https://docs.informatica.com/master-data-management/multidomain-mdm/10-4-hotfix-2/configuration-guide/part-5--executing-informatica-mdm-hub-processes/using-batch-jobs/batch-job-thread-configuration/multi-threaded-batch-job-properties.html

As per Rahul's suggestion earlier, you can use this KB# Support to basically queue a subset of records for revalidate. Instead of <rnum condition in the Query#3 for update, you can try to replace with particular rowid_object  in the queries of the KB before executing revalidate.

We have not tested this, but it should work in the same way.

hi Anandh,

Can you please confirm - "you are modifying the validation rules since the last load". If not, I will recommend that you revert the data back and send an update using the load job. This should reflect the correct trust. For 9.1, not sure if the data changes will reflect in Trust settings even after you revalidate.

You can just add a filter on the stage mapping to have only that record go thru stage and load job.

Yes, please execute a load job and use KB# 525128 to under revalidate job.

What you may need is to execute the recalculate BVT job for a single record - Recalculate BVT Jobs

The behavior should be same in 9.1.

You should be able to cancel the execution but whether it will halt successfully will depend on the execution point of the job at the time. As it is an unsupported version, we do not have any references for the same at this time.