In Sharepoint 2013 - I have 2 lists with 2 workflows.
List 1 has a workflow that creates a simple list item in List 2. List 2 has a workflow that then creates a new list item back in the first list.
On both lists, the workflow starts automatically when an item is created.
On List 2, the workflow starts with no issue when List 1's workflow creates the item to List 2. However, when the new item is created on List 1 from List 2, the workflow on List 1 does not start.
I have confirmed that all list items are being created by me, the admin, and not System Account.
These 2 workflows are Sharepoint 2010 workflows. Our farm does not have Sharepoint 2013 workflows enabled.
I do not have access to make any system changes to the farm. I am merely a Site Collection Admin for my sites.
Please help! Thanks!
Same result in my local farm, while this would be internal logic for recursion prevention just like SharePoint 2013 workflow.
https://blogs.msdn.microsoft.com/sridhara/2014/08/19/fix-sharepoint-2013-workflow-recursion-prevention-part-1/
If you can't use SharePoint 2013 workflow, try to use event receiver, and add logic to prevent Infinite loop. one demo for your reference
Related
Requirement: 68 words forms being migrated to SharePoint 2013.
Nintex Version: 2013
Case: Each workflow is same.
Issue: Each workflow have emails which needs to send links of current list's display form, edit form or assign flexi tasks notifications. So, can we have one copy of workflow which dynamically sends URLs across lists?
Exploration: Tried re-usable workflow with send and get data. This didn't work as each instance of re-usable workflow have unique GUID. Am I missing anything?
I'm creating a SharePoint 2013 visual studio workflow (not a .NET 3.5 workflow). At the beginning of the workflow I assign permissions to the list item the workflow is attached to (by making use of a custom WCF service), and once the workflow has completed, I reset the permissions to a previous state.
The problem I have is that when the workflow gets cancelled/terminated (by the user) before the end of the workflow is reached, the list item permissions need to get set back to a previous state, but because the workflow is cancelled/terminated before the end of the workflow is reached, I can't change the permissions.
Is there a way for me to react to the workflow being cancelled/terminated, which will allow me to set the list item permissions back to its previous state?
Thanks
Have you tried to add even reciever from one of the fallowing:
I created a global reusable workflow in SharePoint 2013 using SPD. I associated the workflow with a specific content type. This workflow is now available in all sub-sites in lists that I bound the this specific content type. This all works pretty well.
However, the IT department wants to only use the one approval task list in the root site. Every time a user updates the list in a sub site, the workflow starts running in that sub site and routes to an approval task list in the sub site. I want all the workflows for my content type in all the sub sites to use the approval task list in the root site.
Is this possible? If not, any work around suggestions?
Thanks in advance.
Riaan
Doesn't appear this was ever answered, but no, every workflow running has to have a task list in the same site. You'd have to develop a task list rollup to get that type of functionality.
OK, this is a first. I created a workflow for a list in sharepoint designer, its a basic if\else 1 step workflow, if an items been created or modified, it sends an email. After a few revisions (make a change, publish, test, repeat...) a weird issue started, Im now getting several copies of the same email sent to me. Not 2 or 3, but hundreds. After about 20 minutes, they seemed to have slowed down, but Im concerned because I have no clue why they started in the first place.
Were running WSS 3.0, and Im using Sharepoint Designer 2007 SP1. Any help would be greatly appreciated.
Did you create an endless loop by any chance?
That is: Is your Workflow set to execute when an item is modified, and does the workflow modify the item?
Prior to SharePoint 2007 SP2, this will generate an infinite loop:
Workflow starts because the item is modified
Workflow modifies the item
Because the item was modified, another workflow will start
The other workflow modifies the item again
Because the item was modified, yet another workflow will start
Repeat until server crashes
In SharePoint 2007 SP2 this was changed and recursive workflows are forbidden now, but it looks like exactly that is happening with your workflow.
The reason it slows down after a while is possibly because the SharePoint or Mail server is starting to get overloaded.
Which version of WSS 3.0 are you running? Check in Central Administration -> Operations -> Servers in Farm and verify against this table. SP2 is version 12.0.0.6421, any lower version is vulnerable against the infinite workflow loop.
To preface, I am working with SharePoint Server 2010 Beta 2, Visual Studio 2010 Ultimate RC.
I have built a custom Content Type based on the Item type with a few custom site columns. I also have built a custom Sequential Workflow using Visual Studio 2010. This is a relatively simple workflow that creates a task, waits for the task to complete, sets the workflow to complete. I am able to deploy this workflow to the site collection through VS 2010 deploy (which is pretty nice, btw). The problem I have is that when I try to associate the custom Content Type with my custom workflow, that workflow is not listed in the workflow templates to choose from. There are only the OOTB SharePoint workflows to choose. The kicker is that if I create a list and associate a workflow to that list, my custom workflow is in the workflow template list. This makes sense since at the start of building a custom workflow in VS2010, one of the first questions is whether the workflow is a Site or a List workflow and I selected List. Is the issue that List workflows are not allowed to be associated with Content Types?!?
Thanks.
In your workflow's elements.xml, look for AssociationCategories and change it to ContentType like so:
<AssociationCategories>ContentType</AssociationCategories>
Big thanks to my co-worker, Yves for pointing this out :)