Skip to main content
Nintex Community Menu Bar
Solved

Call a Workflow showing Unconfigured

S
Forum|alt.badge.img+4

I have this happen occasionally.
I have an action that calls another workflow. At the moment it is saying it is “Unconfigured”

Everything looks good. If I Test with Workflow Testing, both workflows work perfectly.
It will not let me publish because it is “Unconfigured.”  In the past the only way I have solved it is to recreate the “Call a Workflow” action and it works even thought the same variables are used.

It doesn't say anywhere what is unconfigured and everything looks right. I don’t really want to rebuild this as there are about two dozen variables sent over.
 



 

 

Best answer by Scottg

I ended up creating a new Call a workflow action and readdign in al lthe variables.
IT then allowed me to publish.
Every variable was identical so it should have worked. I even made a change later to the destination workflow and after exiting and getting back in the new variables were visible with no error.

I opened a case with Nintex with screen shots, I feel something is wrong.

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

7 replies

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • SimonMuntzNintex Employee
  • Nintex Employee
  • 2436 replies
  • July 28, 2024

Hi @Scottg,

I'm sorry to hear that you are having this issue. At this stage, the only advice I have would be to clear the browser cache and then try to configure that action again.
If the issue persists, I suggest that you raise a case with Nintex Support so that the issue can be sent to the development team for further investigation.

Translate
Get a flying start and additional functionality at: https://gallery.nintex.com/
S
Forum|alt.badge.img+4
  • Scottg
  • Author
  • Scholar
  • 23 replies
  • July 29, 2024

Thanks @SimonMuntz . I’m hoping to avoid reentering all the variables but will if I need to.

I was hoping this had happened to others and peoples had a fix. This has happened to me several times.

Translate
S
Forum|alt.badge.img+4
  • Scottg
  • Author
  • Scholar
  • 23 replies
  • Answer
  • July 30, 2024

I ended up creating a new Call a workflow action and readdign in al lthe variables.
IT then allowed me to publish.
Every variable was identical so it should have worked. I even made a change later to the destination workflow and after exiting and getting back in the new variables were visible with no error.

I opened a case with Nintex with screen shots, I feel something is wrong.

Translate
F
Forum|alt.badge.img+2
  • FranF
  • Rookie
  • 5 replies
  • August 15, 2024

I am having the same issue, is this a defect?

Translate
SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • SimonMuntzNintex Employee
  • Nintex Employee
  • 2436 replies
  • August 16, 2024
FranF wrote:

I am having the same issue, is this a defect?

Hi @FranF,

Please raise a support case with Nintex Support via the customer portal to investigate this issue further to see if it is a defect.

Translate
Get a flying start and additional functionality at: https://gallery.nintex.com/
S
Forum|alt.badge.img+4
  • Scottg
  • Author
  • Scholar
  • 23 replies
  • August 16, 2024

Support was only able to replicate the issue is if a variable is renamed. 
This causes confusion on the system.


This may be what happened. I remember fixing a typo in a variable name but I don’t recall if it was a variable used in the component workflowstart.

Translate
F
Forum|alt.badge.img+2
  • FranF
  • Rookie
  • 5 replies
  • August 18, 2024

Ah, yes I had renamed the ‘call a workflow’ action. That must have been the cause of the problem.

Translate

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie Settings

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