Skip to main content
Nintex Community Menu Bar
Solved

Expired Access Tokens -- Design flaw with Nintex?


Forum|alt.badge.img+4

Got a call from a user that there were a bunch of issues with some workflows. Turns out that the access token used in one of the connections in the workflow had expired and needed to re-authenticate. OK --- Easy fix to re-authenticate and get the workflows to start working again.

 

BUT

Having workflows fail for this reason is NOT acceptable. I’m looking for a solution to be proactively notified BEFORE a workflow failure happens that a connection has an expired token. This way I can assume 100% uptime in my workflow by renewing the access token BEFORE there is a workflow failure.

The connections screen in NWC only shows the date the connection was created. No where is the expiration date documented. 

So how is a Nintex admin to know when these things expire?

Currently the only solution is to wait for a failure (and some angry customers) and then reactively address it by re-authenticating.

This seems like a huge design flaw in this product that should be addressed by the dev team.

Best answer by Sasan

@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.

View original
Translate
Did this topic help you find an answer to your question?

6 replies

Sasan
Nintex Employee
Forum|alt.badge.img+11
  • Nintex Employee
  • 129 replies
  • Answer
  • January 7, 2023

@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.

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • November 30, 2023

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

Translate

Forum|alt.badge.img+7
Sasan wrote:

@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.

Translate

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2436 replies
  • January 29, 2025

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.
 

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • February 12, 2025

Hi ​@SimonMuntz : The link leads to “Project not found”

Translate

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2436 replies
  • February 12, 2025

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

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings