That is strange. I've never had that happen. Which version of Nintex do you have?
During those times when you get an error, are you trying to display in the log the same type of information or is it different?
Don't exactly know what you mean. I just put a reference variable to display. Sometimes I have some text and the a variable. Sometimes just text. I've seen this a number of times.
I have the same version as you and am encountering the same issues. It's not just with the Log History action though. I've had it happen with a number of actions. Usually I can close the action, then reopen it and it will work fine. Really annoying though when it happens. Maybe this is a bug with this version. Have you sent anything to Nintex support?
, it seems like we have a Nintex bug.
I'm now experiencing this as well, on an on-prem workflow in the Query List action. It was working about 30 minutes ago and now when I go to save the workflow (with no changes to this action), it gives me this:
However, my action is not greyed out, as mentioned his was.
If you notice, the Action, Labels, Common, and Variables menu items are all grayed out. This is an indicator that there is an issue and you will get the error. When I see this, I will close out the action, and reopen it, and it will resolve the problem. It seems that when the action opens, those components aren't loading, so the action things the Action Title is missing, which is why it's throwing the error.
Oh THAT action button. Got it. Thanks
Closing and reopening the action (several times) did not resolve for me :/
Hmmm....Well, you could try...
Hi,
sometime, it is also internet browser problem. It happend to me, that some action should be configured twice, because if the nice behaviour of the browser.
Maybe you can only check the issue in other browser or update to the newer version of NW.
This is still happening - Do we have any kind of bug updates on this one?
I'm using IE and am on the newest version of WF. (This was happening in the last version of WF as well.)
I noticed this happened when I copied an instruction from one side of an if-statement to the other. Deleting the pasted instruction and re-creating by hand resolved the problem for me.