Hi friends,

I did some digging into this, and it seems like this is a bug with the Jira Software Cloud integration. Our team is aware of the issue and is working on a fix. I've added your email addresses as another affected members. That does a few things:

• Bring this to the attention of the integration developers
• Help track and prioritize fixes
• Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

I appreciate your patience and understanding.

+1 - Have re-connected to Jira, replayed the run, duplicated the Zap and still getting the same. Here’s hoping for a fix soon!

This is a heavy impact to our business as well.  Escalation of this issue would be greatly appreciated. 

@ken.a you mentioned being added to the bug ticket , but I have not received a notification with a link to that ticket, can you please provide it here? 

Thanks!  

Hey @SamB and @Crrip ,

We started to experience the same exact issue today.  I have confirmed that replaying the run results in the same error message. This integration was working as of yesterday without any changes to the Zap.  I have also confirmed in the editor that that I am able to test the connection without issue, refresh fields and execute the Zap successfully from Test.  We have multiple Zaps to Jira and they are all failing with the same error message.  

Any recommendations on how to address this would be greatly appreciated.  Thanks!

Hello, just to report that we are also being affected by this. A zap that was working 100% since 2022 started to fail with this message. Is there any list to subscribe to be alerted when this is fixed?

Thank you @ken.a - I appreciate your response and the updates that you have provided.  However, we are now approaching two weeks of this integration not working.  Do you have any updates that can be shared regarding the status of the issue?  Is there anything that I can do to help escalate the issue?  If there is not an ETA for a fix soon, we will need to look into implementing a different solution. 

Thank you again for the updates and I remain hopeful for a quick resolution.  

Hi friends,

I have added all of you to the open bug report. We will keep you in the loop via email once the bug has been fixed.

@jsdayton, unfortunately, I can’t provide an exact ETA for the bug’s fix. However, please keep an eye out on your email or on this thread for any updates.

I appreciate your patience and understanding.

Hi @ken.a 

I’m also experiencing issues with the Zaps connected to Jira, since a couple of days ago, and it’s affecting our business operations.

Please add me to the affected users and inform us when it’s fixed!

Hello!

Our Zaps are failing too. It’s impairing our business operations.

Please add me to the list and inform me when it’s resolved.

Hi @jsdayton,

I took a look at the bug report, and it seems like our Engineering team is still closely investigating this issue. However, I’m seeing one report that replaying the Zap run fixed the issue for one user.

Hopefully, this helps.

Hey there @Crrip! 

I did some digging but couldn’t see any bug reports open for that exact error. However I did find a bug report regarding Jira Software Cloud app connections expiring too frequently so I wonder if perhaps the connection may have expired as the Zap was triggering and that caused the error. Do you think that might be the case?

To help determine that can you try replaying that run of the Zap and let me know whether that’s now able to run successfully? Note: if you are running into that bug then you may need to reconnect your Jira account again if it’s expired again and then try replaying it. 

Let me know how you get on with that and we’ll go from there! 

Hello this is affecting our bussiness too it started couple days ago

@ken.a We are also looking for an update to the status.  Can you include us in your communication for updates on this issue.  Thanks!

Hey folks,

I have good news - the bug has been resolved! 

So that error should no longer be appearing. That said, if you continue to have issues despite having the correct permissions do let us know. 

In the meantime, happy Zapping!

@ken.a Do you have an update on the status of this issue?  This is continuing to have a business impact and I would like to avoid having to implement another option/solution.  Any update on current status or an ETA would be greatly appreciated.  Thanks! 

Happening on our zaps too.  

Hello, i have the same problem with a zap that was working perfectly fine until this morning when this error popped up

The same situation is happening with us. This issue has escalated into a significant problem. We depend on numerous zaps to automate Jira issues, and they have ceased functioning for the past two days.

Hello @ken.a, i would like to ask you to add me to the mailing list since we are facing the same problems with one of our zap without anything changing on the zap itself. Rerunning and republishing didn’t changed anything.

@ken.a Same bug here for the past two days affecting a few zaps that have been in place for over a year. Would really appreciate being added to an email list or bug ticket too. Many thanks.

Please add me to the list, I have the same bug.
Thank you.

@ken.a We are having the same exact issue as well. Started 8 hours ago or so.

Please add us to the list to be notified when this is resolved.

Same here - this is heavily impacting our business and ability to operate.
What is the current ETA for resolution?

Can I also be added to the relevant ticket, please?

Maybe @ken.a can add you to the notifying list when it’s fixed.

Same issue over here. Testing Jira connection confirms it is connected and working. Turning zaps on and off and retesting them all still results in the same error message.