New-PWDocumentVersion Error/Exception Handling

The New-PWDocumentVersion cmdlet has been updated to return a more informative message if/when and error occurs. Look for the update in a future release of the PWPS_DAB module.  

I have the same issue with Update-PWDocumentAttributes.   It will start to fail over and over, failing to allocate memory around the 30,000th document process. However, instead of triggering the try catch, it continues until PowerShell hangs and quits.  I tried it with and without the -ErrorAction Stop.  

I am managing thousands of documents.  Today, when using PowerShell to create new document versions using New-PWDocumentVersion, two documents out of a thousand failed (for no explicable reason).  The only notification is an error printed to screen:

Error changing document 'XXX.dwg' to new version

Because it's not raised as an exception I cannot detect the error and the next command in my script overwrites the old version and the previous data is lost. 

How do I detect these errors?  I need an update on this please, because as it stands now I will have to stop using PowerShell.

This is another example where a command has failed but not raised an exception in the expected way.  This time using the Set-PWDocumentState cmdlet.  Is there a way to capture/detect these errors and then stop the script running?

PS C:\WINDOWS\system32> Get-PWDocumentsBySearch -FolderPath $pwfolder -FileName $theFile  | Set-PWDocumentState -State $stateShared | out-null

Failed to change state to 'Shared' for 'XXXX.dgn'. Error: 58268

I have recreated the source of the error: the $verString was invalid as it was identical to the current version. 

However this request is rather to to ask that when errors happen they are correctly raised as exceptions so that they can be detected.  See this try-catch which fails to catch the error: