Best answer

Devops connection is throwing "Client secret is expired.".

  • 11 September 2020
  • 57 replies
  • 1987 views


Show first post
This topic has been closed for comments

57 replies

Same issue here.

@Danvers 
Can you please add me to the affected user list as well? Thank you

Please add me. 

 

We cannot proceed to evaluate Zapier to use it in upcoming important projects if this is not resolved.

Userlevel 2

I have asked @ azureDevOps on twitter for a timeline for this fix if you want to lend your voice to it’s importance. https://twitter.com/Enufacas/status/1309122403742748674

Please add me to the list of affected people as well.

Userlevel 1

I’m affected as well, and use this for investigation into security alerts.  Please let me know feedback as the ticket progresses with MSFT.

Userlevel 7
Badge +11

@Kathy M, @larstj and @Tom de Ridder I’ve added each of you as an affected user on the issue. This means that you’ll get an email when we have an update and lets the Azure DevOps team know how many users are seeing this issue. 

 

The Azure DevOps app is owned and maintained by their team, so I’m not able to give an estimate of when this issue will be resolved. I did find this thread in the Microsoft Developer Community  which looks like someone has reported the issue there. On September 14 there was an update on that thread saying “This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.”

 

I’m sorry that there’s not any more that we can do right now. 

We have the same issue.

We are experiencing the same issue. Please let us know when this will be fixed. This is the only reason we are using Zapier.

Userlevel 1

Same issue here. Thanks

Please add me too as we are having the same issue with DevOps. We use Zapier to connect from SmartSheet to DevOps for software mod requests and this is a big deal for us.

Any help you can provide would be appreciated. I don’t want to have to go back and back these manually in DevOps .:nerd:

Kathy

Userlevel 7
Badge +11

Hi @pictowolf, I’ve added you to the issue as well, thanks!

Yeah I’m having the same issue as well.

Userlevel 7
Badge +7

@Flightline Mike I’ve added you as an impacted user on this side as well!

Userlevel 7
Badge +7

Thanks for letting us know, @Opisto ! It looks like Will reached out on 9/15 in response to your ticket. Could you please check your Spam folder to see if perhaps it got caught up there?

I do see that you have been added as an impacted user but want to make sure you’re receiving Zapier communication!

Userlevel 1

@Liz_Roberts  Thank you Liz, I was not contacted by Zapier support though. Anything I should do?

Userlevel 1

Same here and upvoted on MS’s ticket listed above.

Userlevel 7
Badge +7

@jsmircic @jfrench.donan - I have added you all as impacted users as well so that you will be notified once this bug is fixed.

I know this must be frustrating- in the meantime, I suggest keeping an eye on the thread that lumed shared above as it looks like this bug is being worked on by the app’s team. 

Userlevel 1

Same issue.. on top of that i just paid a yearly subscription for zappier in order to use DevOps integration. It was working great while I was still on the free plan. Once I switched to paid plan it stopped working :) Please send info if the problem will be resolved as the DevOps integration is currently the only reason to use zappier for me.

Userlevel 1

​I am also receiving the same error.

Userlevel 1

Hi All,

So sorry you are continuing to be impacted by this bug- I can imagine how frustrating that must be. 

@GengeT & @Rudolf I have added you as impacted users which does a few things:

  • Re-raises this issue with app’s team
  • Adds weight to the issue in their queue
  • Reminds us to update you once this is resolved

@lumed @Opisto @HQZap I see that you all have been in touch with Support who has added each of you as impacted users. @lumed thank you for sharing the Microsoft ticket for others to reference here. You all will definitely be notified as soon as we hear back that there is a fix! 

 

 


Thank you Liz for your support!

this is affecting us as well

Userlevel 7
Badge +7

Hi All,

So sorry you are continuing to be impacted by this bug- I can imagine how frustrating that must be. 

@GengeT & @Rudolf I have added you as impacted users which does a few things:

  • Re-raises this issue with app’s team
  • Adds weight to the issue in their queue
  • Reminds us to update you once this is resolved

@lumed @Opisto @HQZap I see that you all have been in touch with Support who has added each of you as impacted users. @lumed thank you for sharing the Microsoft ticket for others to reference here. You all will definitely be notified as soon as we hear back that there is a fix! 

 

After communicating with Zapier support, they replied us that Microsoft are the owner of the Azure Integration and to create a ticket on their side. We created this bug, but we did not receive any other feedback than they are working on the issue and that they were able to reproduce it …

https://developercommunity.visualstudio.com/content/problem/1182247/zapier-azure-devops-integration-not-able-to-connec.html

Userlevel 1

Anyone knows a Zapier alternative? We use it daily to link betweek Hubspot and AzureDevops and this bug is slowing us down.

Hi, I have the same problem “The app returned “The client secret is expired”.”  When I try to reconnect to Azure DevOps from Zapier.com.  I started a ticket with Zapier.com support. 

All was running well until about Sept 8th 2020 when I started to see that zaps were failing.  Tried to reconnect by removing Zapier from the Authorized OAuth Apps in Azure DevOps.  I am able to remove it.  When I add the AzDevOps connection in Zapier it will create this as an Authorized OAuth App in AzDevOps.  But after testing the connection from Zapier Apps it fails with the error “The client secret is expired” again.

Anyone had any luck fixing this?