cancel
Showing results for 
Search instead for 
Did you mean: 

Error: "Sequence contains no matching element"

Not applicable
6 4 1,978

Products: Nintex Workflow 2010, Nintex Workflow 2013, InfoPath 2010, InfoPath 2013

Summary

When working with InfoPath and Nintex Workflow, you are using "Assign Flexi Task", or "Request Approval" action and selecting "Task content type" to "... task using InfoPath". 

This applies to Nintex 2010 and Nintex 2013 Workflows.

Then when you try to publish you get this error, however you are still able to save the workflow.

The error:

---------------------------

Message from webpage

---------------------------

Server was unable to process request. ---> Sequence contains no matching element

---------------------------

OK  

---------------------------

Symptom

Only able to save the workflow but, not publish the workflow.

Resolution

This applies for both 2010 and 2013 versions.

1. Open the "Assign Flexi Task", or the "Request Approval" action  > Change the Content Type from Nintex Workflow Task to Nintex Workflow task using InfoPath (wording is slightly different based on version and action type but same process)

2. Click Edit Task Form > Edit with Microsoft InfoPath 2010 (or 2013 depending on version)

3. Save your InfoPath form, then publish it back to the site

4. Go back to the "Assign Flexi Task", or the "Request Approval" action, which should have remained open > Click Save

5. Save your workflow

6. Publish your workflow

4 Comments
Not applicable

This can also happen when you have an outdated Outcome Column loaded in the workflow designer (In Office 365).  Save the workflow, reload Nintex wf designer - your task will now show an error and make you reselect the updated task content type and outcome column and you'll be able to publish.

Not applicable

Currently experiencing the same problem above, have tried the above-noted steps but unsuccessful. Any other theories on what may cause this error?

Not applicable

Are you on Office 365? Do you have any tasks? What is the configuration of your tasks?

Not applicable

Office 2013.  The task is a "Request Data".

I read in a separate thread that this error may occur in workflows that contain a copied state machine (carried over from a previous version). 

I've since renamed the workflow and am re-creating each form one by one (publishing in between), which appears to be working, so far.