Review the information below if you experience an outage that affects Revit Cloud Worksharing.
The duration of the outage does not affect the behavior of either Revit or the Personal Accelerator (PAC).
PAC will continue to attempt to sync on a regular interval. Each time it attempts to do so, it will encounter an exception and skip that model and move on to the next one in the queue. This will happen in the background and you should not see any error dialogs.
For Revit, the intended behavior is exactly as it was for Revit Server Enterprise: Revit will let you continue to work with elements already in your ownership, but it will not let you do anything that requires a change in permissions state, as that would cause the local copy to become potentially incompatible with the central. For this and a few other operations, you may experience delays in the operation while it tries to connect to the services but the operation will eventually succeed when service is restored.
- You can click Save to save locally.
- New users will not be able to open models.
- There is no risk of corrupting the data in the cloud, as there is no way to commit partial data to the cloud.
- Use the following process to identify the most recent local model on a machine. See
Revit Cloud Worksharing: Finding local copies of files.
Note: You will need to do this for the host and linked models.
- When the latest model is identified, copy it to a different location.
- In Revit, open the model detached.
- Click Save As to save it to a network location with the appropriate file name (the file will be <fileGUID>.rvt in the Collaboration Cache).
- When all of the models are saved locally, be sure to re-path the links.
- Have all users cut new locals from the new centrals and continue working.
- Have all users sync to central and close the model.
- Open the central models and reinitiate worksharing to the cloud.
- When all of the models are back in Revit Cloud Worksharing, open them and load the linked models.