Reload Latest: Operation canceled due to some post error

[Anonymous]

Not any particular post error, just "some" post error...  but I digress.

Calling Document.ReloadLatest on a Revit Server based workshared file seems to be throwing some exceptions that the user doesn't see when running SWC through the standard UI.

Background:  I've had to override Revit's implementation of SWC and RL to achieve some key functionality. 

To clarify, if I call it through the API I get the following:

Autodesk.Revit.Exceptions.OperationCanceledException  <- this seems to happen when two users sync at nearly the same time.

or

Autodesk.Revit.Exceptions.RevitServerInternalException

BUT:  only sporadically.

My question is why does an end user not see these but I'm seeing them, is Revit swallowing them and just trying again until it gets through to the server?

Is there any guidance for API developers trying to support Revit Server based worksharing?

If nobody has any insight, I'll see if I can dream up a way to make a reproducible case but being Revit Server Based, it's somewhat more complex.

[jeremytammik]

Dear Ken,

Thank you for your query.

I'm checking with the development team for you...

Cheers,

Jeremy

[jeremytammik]

Dear Ken,

Thank you for your patience.

One aspect of this is that the Revit API should never leak a RevitServerInternalException.

I therefore logged the issue REVIT-113310 [Document.ReloadLatest leaks RevitServerInternalException] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.

Can you possibly provide a minimal reproducible case for the development team to analyse?

http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team, and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

• Impact on your application and/or your development.
• The number of users affected.
• The potential revenue impact to you.
• The potential revenue impact to Autodesk.
• Realistic timescale over which a fix would help you.
• In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

Cheers,

Jeremy

[jeremytammik]

Dear Ken,

Thank you for your patience.

The development team analysed the issue REVIT-113310 [Document.ReloadLatest leaks RevitServerInternalException] and say:

I could not reproduce this issue. Document.ReloadLatest works without any exception when another user's SWC is committed in the middle of the ReloadLatest. Reproducible steps and journals is necessary for us to continue the investigation.

Can you please provide a minimal reproducible case for the development team to analyse?

http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

Please also add the journal files produced when you encounter the problem your end.

Thank you!

Cheers,

Jeremy