Forum Discussion

Marc Nemegeer's avatar
Marc Nemegeer
Brass Contributor
Nov 26, 2018

New group - Unable to save 2010 workflow

Hi,

I created a new tenant using "Microsoft demos". I create a new group site collection in there, so I have a new site collection.

When trying to create a 2013 workflow in there and save it, it works. A 2010 workflow can be created but NOT SAVED and NOT PUBLISHED. Can this be solved ? Anybody know the reason for this ?

Best regards,

Marc

6 Replies

  • simranjit Singh's avatar
    simranjit Singh
    Copper Contributor

    We are facing the same issue in our tenant. Sharepoint 2010 workflows are not getting associated with the list, however sharepoint 2013 workflows are working fine. The only difference is that in our case we are facing this issue in classic Team site. We have not tested this scenario in a group connected team site. A support case was opened with Microsoft . It has already been 2 weeks and MS team has not been able to figure out the cause and fix.

    • jcgonzalezmartin's avatar
      jcgonzalezmartin
      MVP
      Mmm...seems something is wrong with legacy workflows in SPO. Best you can do is to open a support ticket
      • simranjit Singh's avatar
        simranjit Singh
        Copper Contributor

        We figured the root cause of the issue in our case with the help of Microsoft. The cause of the issue is that the ‘Title’ column was set as ‘Required’ on the ‘Workflows’ list of the site.This list is a hidden list and when any column is set to ‘Required’ it prevents major versions of the workflow files to be visible to users and also prevents them from getting published.Also on the hidden ‘Workflows’ list  ‘Require documents to be checked out before they can be edited?’ was set to Yes. This should be set to No

         

        We do not know who modified the setting as user is saying he did not do that change and the site was not a migrated site. We are investigating on that.

  • You need to go and explicitly add yourself as site collection admin to the site using set-spouser -loginname user@domain.com -isssitecollecitonadmin $true for whatever reason group sites site collection admin doesn't act the same as being explicitly assigned to the site.

Resources