Stop-AzSynapseTrigger powershell command no longer working

Question

Stop-AzSynapseTrigger powershell command no longer working

- 31 Microsoft Employee

Hi,

Recently the Stop-AzSynapseTrigger powershell command has stopped working for us.

It's giving the following error:

PS C:\Users\user1>  Stop-AzSynapseTrigger -WorkspaceName "workspace-name" -Name "my-trigger"
Stop-AzSynapseTrigger : {}
At line:1 char:2
+  Stop-AzSynapseTrigger -WorkspaceName "workspace-name" -Name "my- ...
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Stop-AzSynapseTrigger], Exception
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Synapse.StopAzureSynapseTrigger

It was working fine until about 1 month back, but now its throwing this error.

Other powershell commands like Stop-AzSynapsePipelineRun, Invoke-AzSynapsePipeline, etc are working fine.

Please suggest the fix.

0 comments

4 answers

Your answer

Answer 1

Alex Cruickshank 0

Hi

Any updates on this please? I am facing the same error.

Thanks

Bhargava-MSFT 31,361 Reputation points Microsoft Employee Moderator

2023-05-12T18:20:37.65+00:00

Hello Alex Cruickshank (AXK),

Thank you for reaching out on the Q&A forum.

The command stops the trigger even though it throws the error message. Please ignore the error message for now. We are checking with the internal team to fix the error.

https://github.com/Azure/azure-powershell/issues/21705
Alex Cruickshank 0 Reputation points

2023-05-12T18:22:49.4333333+00:00

Hi, I can see it stops them but it causes my DevOps pipeline to fail because it exits with an error
Bhargava-MSFT 31,361 Reputation points Microsoft Employee Moderator

2023-05-12T18:27:10.85+00:00

Hello Alex Cruickshank (AXK),

Sorry about that. Please allow us some time to check with the internal team and fix the error. I will keep you posted.
- 31 Reputation points Microsoft Employee

2023-05-12T18:31:12.02+00:00

@Anonymous Maybe you can wrap it in try-catch block and ignore the error. But of course the problem with that will be if there is a real failure, it'll be missed.
Patrick Neal 0 Reputation points

2023-05-23T17:50:33.1933333+00:00

Any update on this?
Bhargava-MSFT 31,361 Reputation points Microsoft Employee Moderator

2023-05-23T18:39:31.01+00:00

Hello Patrick Neal and Alex Cruickshank (AXK),

<update>

Our engineer submitted a fix and waiting for the release cycle. I will update this thread once the fix is deployed.
Bhargava-MSFT 31,361 Reputation points Microsoft Employee Moderator

2023-07-12T19:38:47.03+00:00

Hello Patrick Neal and Alex Cruickshank (AXK),

<update>

The fix has been deployed.
Jacob Wadowski 1 Reputation point

2023-10-12T19:54:27.8566667+00:00

Still experiencing this issue. Command successfully stops the trigger but causes DevOps pipeline task to fail (when ErrorActionPreference = Stop).

Answer 2

Anonymous

Do we have an ETA for the bug fix?

0 comments

Answer 3

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 4

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

2 deleted comments

Comments have been turned off. Learn more