Issue Summary

The logic to lookup the Approvers-custom field seems fragile and breaks, e.g. when the field is translated.
When the field has a different name in another language and an approver is added by an actor that has that different language selected, the update might be missed and no approval notification is triggered.

This also affects A4J automation. It is not 100% clear what language will be used for the field lookup when performed by the automation user

This is reproducible on Data Center: not attempted

Steps to Reproduce

1. in a classic project
2. app approval to a workflow
3. add a second language to the project
4. translate the approval custom field in that other language (to something else than Approvers)
5. change your users default language to the second language
6. add an approver

Expected Results

An approval notification is generated

Actual Results

No approval notification is generated

Workaround

Make sure all "Approvers" fields are translated to "Approvers" in all supported languages or at least translate to the exact same name in all languages.