The primary reason for an engagement file to encounter issues such as an infinite loading screen when adding risks is due to the Engagement file name containing special characters.
As demonstrated by the image below.
If your file is:
- A SmartSync file which is internally hosted on a company server, the parent file will need to be deleted (usually by IT), and then the renamed file will need to be published to the server and all auditors with a copy of the file prior to the rename will need to open their child/local copy and go to SmartSync > Delete Copy.
- A SmartSync file which is hosted on the CaseWare Cloud, the parent file will need to be deleted, and then the renamed file will need to be published to the cloud and all auditors with a copy of the file prior to the rename will need to open their child/local copy and go to Cloud > Delete Copy.
- A Non-SmartSync file, then no further action is required.
Deleting child/local copy of regular SmartSync file:
Deleting child/local copy of CaseWare Cloud hosted SmartSync file: