@jeffoliver1000 Thank you for your input and feedback. We do have this enhancement in our backlog. Your vote in Nintex ideas would help prioritize this.
10 month later and we still run into that issue.,
I can only repeat “This seems like a huge design flaw in this product that should be addressed”
@Sasan : Please push this to a higher priority
@jeffoliver1000 Thank you for your input and feedback. We do have this enhancement in our backlog. Your vote in Nintex ideas would help prioritize this.
We should not be 2 years removed from this with it still occurring. It should be a top priority.
Hi @AUSharePoint,
I will leave@Sasan to reply to your question quoting him.
In the meantime, you could monitor this using a simple daily scheduled workflow.
The Nintex Automation Cloud API has an endpoint that lists the connections in the tenant.
https://developer.nintex.com/docs/nc-api-docs/ref/connections-v1/operations/list-connections
Each connection returns a property of invalid, true, or false. If true, you could email a tenant administrator, etc.
Hi @SimonMuntz : The link leads to “Project not found”
Hi @RonLevy,
Due to Nintex Automation Cloud being renamed to Nintex Workflow recently, the URL has changed.
Try:
https://developer.nintex.com/docs/nw-api-docs/ref/connections-v1/operations/list-connections
@SimonMuntz your link to the NAC API for connections in the tenant looks interesting - but I have no idea how I would use this? Any chance of an example or instructions of how we could use this to create the simple daily scheduled workflow you refer to?
Thanks
Ian
Hi @stricki,
As advised above, the API returns information about each connection.
Example:
{
"id": "0063d447-8505-41e3-a2c8-4a378a6c792f",
"displayName": "SharePoint Integration",
"isInvalid": false,
"createdDate": "2022-01-01T00:00:00Z",
"modifiedDate": "2022-01-01T00:00:00Z",
"contractName": "SharePoint Online",
"contractId": "0518c30c-6e49-408a-90b8-5dd5dd066ed0",
"createdByUserId": "auth0|1234567890abcd"
}
If the connection is not valid, the isInvalid value will be true.
To make connecting to the API easier, I have created an Xtension.
It is configured for the US, so if your tenant is anywhere else, you will need to edit the URL in the Xtension.
I have attached a workflow that loops through all the returned connections and checks if they are invalid.
The workflow logs the invalid connections, but you could check if the variable was not empty, and if so, email it to someone who has access to fix the connection.
