Get-PnPLabel / Set-PnPLabel started throwing error after running fine for 2+ years

[jherschel77]

I have an Azure Runbook that looks for newly created Teams and sets the Documents Library retention label. For the past 2 weeks, it has been failing with this error:
Value cannot be null. Parameter name: Empty correlation Guid -

Here is my code, I've spent a few hours trying to figure it out with no avail. Any thoughts? I did add the -ValuesOnly tag recently, but still fails...

` # Set label for library if NOT already set

        $listName = "Documents"

        $labelValue = $null

        $labelValue = Get-PnPLabel -List $listName -ValuesOnly

        if ($labelValue -eq $null) {  # I also tried $labelValue.TagName

            Write-Host "--  Label Not set - Setting to General Business on $($listName)"

            $setLabelOutcome= Set-PnPLabel -List $listName -Label "Business" -SyncToItems $true

            Write-Output $setLabelOutcome
        }

`

I also just tried skipping the entire 'check to see if it is already set' and that doesn't work either:

Set-PnPLabel -List $listName -Label "Business" -SyncToItems $true

I wonder if some behind the scenes SharePoint stuff has changed....

[Chrdik78]

I have the same issue. PnP.PowerShell 2.12.0. No solution found yet as I need application permissions to set the label with a script on new sites.

[RahulDhiman995]

I am also facing the same issue. I have tried PnP.PowerShell 2.12.0 & 3.12. No solution found yet.
Also I have asked in Microsoft community for the same error:
https://learn.microsoft.com/en-us/answers/questions/4376864/error-applying-retention-label-to-sharepoint-docum

If anyone find a solution then please let me know.

[RahulDhiman995]

I am also facing the same issue. I have tried PnP.PowerShell 2.12.0 & 3.12. No solution found yet.
Also I have asked in Microsoft community for the same error:
https://learn.microsoft.com/en-us/answers/questions/4376864/error-applying-retention-label-to-sharepoint-docum

If anyone find a solution then please let me know.

[Mkaram87]

Same issue for me - does anyone know if there is a fix?

[RahulDhiman995]

@Mkaram87 Checkout this bug as well
#5027