Purpose of problem workflow (Account2ProjectHIEPP):
When the option set (HIE PP) in Account changes, the field by the same name (HIE PP) changes in Project.
1. Created 1:N Relationship - Primary (Project) and Related Entity (Account) - named Project_Account. This Project _Account is also used successfully with 10 additional workflows - when a field changes in Project, the respective field in Account is updated. Note, the correlation is different than the problem workflow.
2. Next, the workflow (Account2ProjectHIEPP) is created. Running this in background will not generate the error that informs of the reason "cannot find record to be updated", so for testing purposes it is run on-demand.
Again, there are 10 workflows that use the 1:N relationship (Project_Account) without problem. However, they are updating from Project to Account.
I thought the solution was to create a 1:N relationship in Account (Account_Project). It was created but I could not load it into the solution.
Anyone, seeing the glaring problem?