Nintex Ideas
đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
Today, we run into the same issue. NAC Workflow failed during assingning permissions with following message:
"The SaaS provider cannot renew the access token, please re-authenticate the connection to renew the access token"
We have some more connections and a lot of business workflows which will need manually interactions because of such behaviour. That is so bad. This will hopefully be fixed soon.
Thank you all for your feedback. Apart from the previously mentioned change that allows token refreshing, we do not currently have any additional items related to this idea in our near-term backlog. Our current focus is on higher-priority features. However, please continue to vote on ideas, as we reassess requests every quarter. We will reach out if our priorities change. Your ongoing feedback is crucial for our longer-term planning.
All our running O365 workflows got stuck which were dependent of component workflows due to new token set by NWC, its important also to set not to expire token or some other work arounds to avoid worklfow failures.
Alerts going out to the admin on upcoming token expiration would definitely be helpful, similar to how you have alerts for upcoming SSO certificate expiration.
I just had a whole batch of workflow instances fail again because of another expired access token. In looking at the age of the connection it was using it was only about 7 months old. Much less than one year. So clearly it's pointless to make a workflow "reminder" as you suggest to send me a reminder to renew the token. Should I just pick some random date to use as the reminder window? This is really getting ridiculous guys!!!
Hi Jeff,
Thanks for the feedback. As mentioned above we did recently add the ability to refresh the token life and are looking to add some alerting around the expiry. I will update here when we have a date for this. In the interim a potentially option would be syncing up your token expiry using this refresh option and create a scheduled workflow to send out a reminder email of expiry.
Because your platform currently offers NO notifications of expiring tokens, nor does it provide a way to automatically renew them or generate tokens that don't expire, we have had to set expectations with our customers that their Nintex workflows could go down at any time because of expired tokens. In other words we've had to let them know we can't guarantee any uptime and things might just stop working as intended unexpectedly and cause negative repercussions to their business processes. In fact we recently had an issue with an expired token that caused about 30 workflow instances to fail, causing a major disruption to a business unit.
Unsurprisingly, the team is not very happy with Nintex at the moment.
Hi Bruno,
We have added the ability to refresh the life of a component token in the latest release. We are also looking at adding notifications to further enhance the management experience. Please let us know if you have any feedback on the changes.
Cheers,
Leigh