A previous post details when how this issue occurs and how to avoid it form happening. However, this mismatch may have occurred before it was avoided. Thankfully if this issue does occur there is a fix for it.
The first step to addressing the issue is to identify the Task and what state it is in (inProgress, completed, etc.). Then, do the same for the PEX object but when looking at the PEX object make note of the GuID value at the end of the URL.
What the user will have to do is run a POST API call against the PEX object that will transition it into the same lifecycle state as the Task. For example if the PEX is marked as complete and the Task is marked as inProgress, then the call will update the PEX object.
For this example the call will be:
https://
By running this call it will transition the current state of the PEX object into Completed back to inProgress. Once this is in place go into the Admin & Settings > Signature Policies. Here, make sure that PEX and Task objects have the same Signature Policies. Then, run your Tasks again and both objects should be in sync.
