You are viewing limited content. For full access, please sign in.

Question

Question

An error occurred while saving the workflow. [0343-WF1]

asked on October 29, 2017

Hi Guys

I am currently getting an error on my workflow designer, if I add a conditional branch and build the branch it sometimes saves and works and sometimes not.

And even if I disable the newly build branch, it gives me this error.

What I can not understand is that it will not even publish my workflow to the point where it was working 100%

Can anyone help with this problem, as this is becoming a major pain? 

Regards

Workflow error.JPG
0 0

Replies

replied on December 17, 2018

I found out that the "For Each Value" activity was causing the issue.

I recreated it exactly and deleted the activity and was able to publish.

3 0
replied on November 28, 2017

I've found that copying the branches with activities in them causes problems.  I've resorted to dropping in new branches and then copying the activities.  Not sure if this will help, but in a small workflow this has been the easiest and fastest thing for me to do.

2 0
replied on November 28, 2017

Yes i found that to have been to work around for now.The problem is when the workflow gets bigger.

Thanks for the comment Ken.

0 0
replied on August 8, 2018

I was able to recreate this and was able to narrow it down to copying of a for each value action from one workflow to another (after copying I did modify the properties of the "for each value" to work with the workflow it was copied into).

 

Failed to publish workflow 'Alchemy Import - Individual Insurance': An error occurred while saving the workflow 'Alchemy Import - Individual Insurance'. [0343-WF1] [0411-WF0]
An error occurred while saving the workflow 'Alchemy Import - Individual Insurance'. [0343-WF1]
---Stack Trace---

   at Laserfiche.Workflow.ComponentModel.WorkflowSerializer.SaveWorkflow(IWorkflow workflow, XmlWriter writer, Boolean throwError, IWorkflowUI workflowUI)
   at Laserfiche.Workflow.Designer.PublishWorkflowAction.InnerPublish()
   at Laserfiche.Workflow.Designer.PublishWorkflowAction.InnerPublishWithProgress()
   at Laserfiche.Workflow.Designer.PublishWorkflowAction.Execute()

***

Object reference not set to an instance of an object.
---Stack Trace---

   at Laserfiche.Workflow.Activities.ForEach.ForEachValueActivityProxy.WriteProperties(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.ActivityProxyBase.WriteXml(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.CompositeActivityProxyEx.WriteCustomXmlElements(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.CompositeActivityProxyEx.WriteCustomXmlElements(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.CompositeActivityProxyEx.WriteCustomXmlElements(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.CompositeActivityProxyEx.WriteCustomXmlElements(XmlWriter writer)
   at Laserfiche.Workflow.Activities.Proxies.SequentialWorkflowActivityProxy.WriteCustomXmlElements(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.WorkflowBase.WriteXml(XmlWriter writer)
   at Laserfiche.Workflow.ComponentModel.WorkflowSerializer.WriteWorkflowToXml(XmlWriter writer, IWorkflow workflow)
   at Laserfiche.Workflow.ComponentModel.WorkflowSerializer.SaveWorkflow(IWorkflow workflow, XmlWriter writer, Boolean throwError, IWorkflowUI workflowUI)

***

 

1 0
replied on August 8, 2018

This issue has been fixed in Workflow 10.2.1.

1 0
replied on November 6, 2017

There isn't enough information to troubleshoot. If you right-click on the help button, there should be an option to "copy diagnostic data" which might give us more information.

0 0
replied on December 29, 2017

Hi Christo,

I just ran into this same issue ([0343-WF1]) which is how I found your post. Thankfully, I was able to find an easy fix: I saved a copy of the workflow to my desktop, closed the Designer, re-opened the Designer, opened the saved workflow on my desktop, and published without issue.

I hope the above steps will help you in the future!

~Rob

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.