Office Online Server is taking long time to perform the auto-save operation

Question

We integrated Office Online Server in our web application and in the WOPI web integration we are setting File URL properties such as FileUrl. This URL points to /wopi/files/{file_id}/contents link and internally, it will call the API once we start editing the document.

From this API, we are updating the file version but the issue is that after editing the WOPI document, the triggering of the API /wopi/files/{file_id}/contents is taking a long time and we are unable to find how it is getting triggered? Is there a way we can trigger this method directly?

Answer 1

So if I get it right it takes a long time BEFORE the /wopi/files/{file_id}/contents endpoint is hit. In such a case, I'd recommend four things:

1. Run the WOPI host in a debug mode and trigger the endpoint from the OOS machine manually and see if there are any delays related to the network infrastructure.
2. Checking whether you set the WOPI host capabilities right in the CheckFileInfo. If you set the WOPI Client's expectations incorrectly, it may take time for it to figure out what's going on and potentially fall back to a different method.
3. Using the WOPI validator app
4. Checking the event viewer for any errors related to a specific Session ID and Correlation ID