this has not happened previously, but just started in the last set of workflows we've deployed. no specific reason why this is happening, but is frustrating nonetheless
Page 1 / 1
Hi,
I checked with the Nintex Development teams and they advised that there were no maintenance or other issues at the time you saw this issue.
There were no support cases for this issue that I am aware of.
As this is the case is it possible that the issue is comming from exchange?
I checked with the Nintex Development teams and they advised that there were no maintenance or other issues at the time you saw this issue.
There were no support cases for this issue that I am aware of.
As this is the case is it possible that the issue is comming from exchange?
Reply
View our Community Site Map
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.