I am having problems running the connector.
When using the correct Document GUID (either with or without the curly brackets) The connector fails with a 'BadGateway' error.
"code": 502, "source": "uk-001.azure-apim.net", "clientRequestId": "bf53866f-0f29-4393-9b77-17350fb878c7", "message": "The response is not in a JSON format.", "innerError": "Cannot read server response." }}, clientRequestId: bf53866f-0f29-4393-9b77-17350fb878c7
If I enter an incorrect GUID the connector returns a 'Document NotFound' error as expected - although the full error does not seem right:-
"statusCode": "notFound",
I'm having a similar issue with the Fetch documents by saved search. Works fine when the search returns nothing but when the search returns a dociment(s) I get the same error. The error message seems to indicate that the response from the server is not valid json.
We have noticed that in some situations saved search fails when document attributes are requested. The work around for this problem is to select no environment in Find documents by Saved Search. The action will return documents but without environment attributes. If you need attributes, you can use Find Document by path or GUID action for each single document.
It is a known issue and will be fixed in future versions of ProjectWise/WSG.