In SharePoint 2013, workflow runs with the users permissions unless it has an app step with elevated permissions. If your list has unique permissions, ensure that your workflow history list and task list have write permissions for the user.
Another item to check for are steps in the workflow where the user do not have permissions to do. One instance is if the user has no delete access on the list but there is a step in the workflow to delete an item in the list. This was not an issue in SharePoint 2010 as the workflow was running as system account.
Also, do not make your workflow to depend on or read the last modified date on the item. Because the workflow will change it.
Another item to check for are steps in the workflow where the user do not have permissions to do. One instance is if the user has no delete access on the list but there is a step in the workflow to delete an item in the list. This was not an issue in SharePoint 2010 as the workflow was running as system account.
Also, do not make your workflow to depend on or read the last modified date on the item. Because the workflow will change it.
Comments