Today, we are noticing issues while publishing workflows. These workflows worked yesterday. But we could not publish today. Is this due to Task id change?
Does anyone else see similar issue while publishing an already published O 365 workflows?
This morning I noticed this message on workflow designer screen:
Fix for the issue is to just republish the workflow. I was able to republish and everything went well!
Also the task id screen is back to original format (no radio buttons for Task GUI and Task id).
Good job for a quick turnaround Nintex Support
Try reverting the changes made and then publish it ?
Does it still throw the same error ?
You can even try exporting / importing the workflow
What do you mean by Task id change?
What's New: Office365 - Query Task IDs for Multiple Approvers
No, that certainly isn't caused by the new feature.
I would rather look back to the changes you have made. Maybe you have an action that lost relation to a variable? Or you changed something in your SharePoint, ex. field from single option, to multiple options?
Can you revert your changes, publish workflow, and then proceed with them step-by-step looking what's causing the issue?
When I have such problem, I do the following:
You can as well check the https://status.nintex.com/ - maybe something was wrong with the designer service at that moment?
I have the same exact error sinds 04/10. The error also occured after I tried using the new Task ID functionality with the Task process action.
I've tried to create a collection in the Task process settings and got the following warning: "Command: undefined - process". Thinking that something went wrong I checked all my variables and I could see the newly created variable there. I thought this was strange so I've removed the variable and then remove the Task process action.
Since then I can't publish my workflow anymore... Didn't do anything else besides adding this action and collection variable.
I've opened a support ticket and they are looking in to it. I'm "glad" I'm not the only one running into this problem.
Received this email from support team:
Our Dev team has found the following: Issue was related to action changes on "Actionable Emails" and "Task ID" changes. We have since removed these features and those workflows that had it will need to be republished. They did confirm that the issue was due to new changes pushed on Oct 3. But I think this was nor affecting all tenants.
My bad I was sure they did regressions tests
Kiran Bellala i think you should mark your last answer as correct, as it most completely answers your own problem Do you agree with me?
Retrieving data ...