Start-AzSynapseTrigger throws error but starts the trigger

[sarajag]

Description

When using the {Start-AzSynapseTrigger} PS cmd in Azure Powershell 5.0 task in Azure DevOps pipeline, the cmd fails with the error
"Request operation requires element of type Object byt target is String"
However, in the background it would have started the trigger.

Issue script & Debug output

Start-AzSynapseTrigger : The requested operation requires an element of type 'Object', but the target element has type
'String'.
At line:1 char:26
+ ... ach-Object {Start-AzSynapseTrigger -WorkspaceName $workspaceName -Nam ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Start-AzSynapseTrigger], InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Synapse.StartAzureSynapseTrigger

Environment data

**************************************
Name                           Value
----                           -----
PSVersion                      5.1.22000.65
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.65
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Module versions

0.11.0     Az.Synapse

Error output

Exception      : System.InvalidOperationException
InvocationInfo : {Start-AzSynapseTrigger}
Line           : $trigs | ForEach-Object {Start-AzSynapseTrigger -WorkspaceName $workspaceName -Name $_.name}
Position       : At line:1 char:26
                 + ... ach-Object {Start-AzSynapseTrigger -WorkspaceName $workspaceName -Nam ...
                 +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 17

Message        : The requested operation requires an element of type 'Object', but the target element has type
                 'String'.
StackTrace     :    at System.Text.Json.JsonElement.EnumerateObject()
                    at Azure.Core.ArmOperationHelpers`1.IsTerminalState(String& state)
                    at Azure.Core.ArmOperationHelpers`1.<UpdateStatusAsync>d__25.MoveNext()
                 --- End of stack trace from previous location where exception was thrown ---
                    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                    at Azure.Core.ArmOperationHelpers`1.<UpdateStatusAsync>d__26.MoveNext()
                 --- End of stack trace from previous location where exception was thrown ---
                    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    at Azure.Core.ArmOperationHelpers`1.<WaitForCompletionAsync>d__24.MoveNext()
                 --- End of stack trace from previous location where exception was thrown ---
                    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                    at System.Threading.Tasks.ValueTask`1.get_Result()
                    at Microsoft.Azure.Commands.Synapse.Common.Utils.Poll[T](Operation`1 operation)
                    at Microsoft.Azure.Commands.Synapse.Models.SynapseAnalyticsArtifactsClient.StartTrigger(String
                 triggerName)
                    at Microsoft.Azure.Commands.Synapse.StartAzureSynapseTrigger.ExecuteCmdlet()
                    at Microsoft.WindowsAzure.Commands.Utilities.Common.AzurePSCmdlet.ProcessRecord()

[dingmeng-xue]

Thanks for reporting. Could you try the latest version of Az.Synapse (0.18.0)?

[PramodValavala-MSFT]

@sarajag The error you are seeing is from the ForEach-Object cmdlet since the output of the Start-AzSynapseTrigger cmdlet is a Boolean value.

This is why the trigger has started with your script failing after.

[KirstenBurnett-weir]

Hello.
Having the same issue as @sarajag all of a sudden on disabling a trigger - was this resolved or is there a workaround? I did force an update of the Az.Synapse module but that has not fix the problem.

[sarajag]

@dingmeng-xue - Thanks for the reply. Reverted back to version 0.7.0 and that worked well.

@PramodValavala-MSFT - Thanks for the reply. I do not think that is the issue, the ForEach takes object from the $trigs and applies it on the Start-AzSynapseTrigger cmd. And this cmd had been working well for more than a month until yesterday. Figured out that it is the problem in the module version

@KirstenBurnett-weir - I changed the module version (to 0.7.0) and it worked, But like suggested you can change to latest version. The problem resolved.

[PramodValavala-MSFT]

@sarajag You are right. Not sure what I was thinking earlier. I am going to reopen this and have the concerning team take a look.