A typical unresolved work object would have a pxFlow list with at least one of the items in the pxFlow list having a pxAssignmentKey referring to an assignment object.
A typical resolved work object would have no pxFlow items in the list.
If you have either an assignment object but no pxFlow item referring to it, or you have a pxFlow item that refers to a nonexistent assignment object, then I would expect one of the repair activities (such as fixBrokenAssignments) to be able to fix the issue.
However, as you seem to have no pxFlow item and no assignment, your work looks more like a resolved one.
Can you say something about how the work got into this state ? If you look at this history elements for this work, what does it show as the last several events that occurred ?
The work is not resolved and it is still in "Pending-vendor" state. we are still investigating the issue to find out - how the work got into this situation. I am trying out find out here - Is there any option to put the work object back on track to move forward in the flow?