Hi Jp,
Perhaps this object does not exist in the database or has already been deleted. This can happen if the object was automatically committed earlier
is there a trick or way to make this work , ...maybe via sub flow or something. i tried though but didint work.. any ideas..
Issue Fixed: Found the sub microflow which was failing but error handling was not managed well in this , this was dropping the object and was continuing to the main microflow , so when the last commit was running it was failing with object not exists. fixed the sub microflow and now the commit works fine.
alternately , another workaround also worked , since it was the last commit , we can just create a new object with the values, but this will not fix the internal sub microflow issue that may come back to haunt later.