Forum Discussion
SPO document library is missing Automate menu option
- Jan 31, 2022
DhirenMehtaMSFT it would be useful to know what the root cause was of this incident please. Automate is now available again and we have tested our flows and all is good - But, we do want to know what happened, especially if it was an update or release of some kind from Microsoft. Thanks.
https://social.technet.microsoft.com/wiki/contents/articles/39331.sharepoint-online-verifying-and-modifying-flows-policy-in-site-using-powershell.aspx
You want to make sure that your Flow policy for the site is set to "NotDisabled"
- EddoriaJan 30, 2022Brass ContributorWho would have disabled the flows?
I have tried the powershell but get the following message (I have deleted company and site name):
Set-SPOSite : https://....sharepoint.com/sites/... is a Groups site collection. The valid parameters for this type of site collection are '-Identity', '-AllowSelfServiceUpgrade', '-DefaultLinkPermission', '-DefaultSharingLinkType', '-DenyAddAndCustomizePages',
'-DisableCompanyWideSharingLinks', '-DisableSharingForNonOwners', '-LockState', '-Owner', '-ResourceQuota', '-ResourceQuotaWarningLevel', '-SandboxedCodeActivationCapability', '-SharingCapability', '-ShowPeoplePickerSuggestionsForGuestUsers',
'-SocialBarOnSitePagesDisabled', '-StorageQuota', '-StorageQuotaReset', and '-StorageQuotaWarningLevel'.
At line:1 char:1
+ Set-SPOSite -Identity 'https://....sharepoint.com/sites/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-SPOSite], ServerException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.SetSite- DhirenMehtaMSFTJan 30, 2022
Microsoft
Eddoria I can't say who would have disabled the flows, but before that, let's verify if the flows are disabled or not. Can you try to hit the URL https://yoursiteurl/_api/site and see the output value for DisableFlows property?
- JanVanNJan 31, 2022Copper Contributor
DhirenMehtaMSFT it would be useful to know what the root cause was of this incident please. Automate is now available again and we have tested our flows and all is good - But, we do want to know what happened, especially if it was an update or release of some kind from Microsoft. Thanks.