Jira For Ticket 401 error

@SinaM Is this something you've just seen in the last few days or has it happened before in the past?

I'm asking because if you check out Jira's status page they have a few alerts from the 4th - 7th that mention problems creating issues. 

I'm wondering if that could be related to what you are seeing?

Its been a month there 
since we started using workflows and jira integeration 

Hey @SinaM - I’ve passed this information over to the team via a conversation and added your issue to an open bug we’re looking into at the moment. Updates to follow via the Messenger 💬

Hi, I’m having this same issue.

It seems like when you install the app (Jira for Tickets on Intercom) for the first time it works fine but eventually the token expires and it is never refreshed. 

Hey @Santiago Alsua 

I see that you were in contact with my teammate Sara. How did it go with that?

Are you still experiencing the same issue? If so, please feel free to reply to us in the same conversation you have with Sara.

Thanks!

Hi there - We also experienced the same issue when we installed the Jira for Tickets app. Jira issues would be successfully created and then suddenly, they wouldn’t and we’d see that 3rd party authorization error. Is there any sort of timeline for when this bug will be looked at? My team has had to pause using this app, as it created a lot of redundancy in ticketing process because the jira issue creation would fail and all they could do was create a new ticket and hope it worked.

Hey @khp,

Checking the issue report, I see that it is still being worked on. I have just forwarded your message to the support engineering team, and you will receive an update via email from us when the issue is resolved.

Thanks!

Hey Ayk,

how about the status? We receive this error on a daily basis and it makes working with it a pain…

Best

Daniel

Hey @Daniel Winklhammer

I have just followed up with the product team regarding a status update on this issue now. You will hear back from our team when we receive any update via email.

We will also post here once this issue is resolved. 👍

We are having the same issue. 

Hey @SinaM @Santiago Alsua @khp @Daniel Winklhammer @Daniel Little 

Thanks again for reporting this issue! We have received an update from our product team, and it looks like they have fixed the issue.

Could you please check it on your end, and let us know how it goes? If you are still seeing new occurrences (from today) let us know, and I can check with them again.

Hi, I just encountered this today:
 

Jira’s status page shows fully operational from what I can tell. Conversation ID for investigative reference: 10162.

Hi @Jonathan Lin -- Cam from the Support Engineering team jumping in here for my teammate Ayk. 

It looks like you opened a chat on this over in Messenger and have since seen this issue appear to resolve itself 👍 As Jorge mentioned in that chat, it looks like this error may have been a one-time blip with Jira, but if you see if occur again please do let us know. 

Thanks for the follow-up, Cameron!

Good morning, the same error is happening to me, from one moment to another I got the “unauthorized” error, I had created a ticket half a day ago and then I tried to create another one and it generated the error, since then I have not been able to create more tickets.

Has anyone found a solution to the problem? 

​@kDm It’s Mat from the Support Engineering Team 😀

This kind of issues are better addressed in the direct conversation with our team - so we can investigate your specific setup.

I recently came across this thread while experiencing a similar issue with the Jira integration. Occasionally, I receive a 401 Unauthorized error when trying to create tickets, which suggests that the authentication token might be expired or incorrectly applied during the request.

I see that this issue was previously addressed, but I wanted to check if the fix is still holding up or if there have been any recent reports of similar problems. I will perform some tests on my end and monitor the behavior, but I’d appreciate any guidance on possible troubleshooting steps if the issue persists.

​@madesigner 

It is silly to say that but:

“Have you tried to reinstall the integration?”

It usually solves the issues with the authorisation.

It’s really silly but you guys just need to go to Jira for Tickets app and then select “Custom Automations” when you use workflows. It all works perfectly fine after that.

I recently came across this thread while encountering a similar issue with the Jira integration. From time to time, I receive a 401 Unauthorized error when attempting to create tickets, which may indicate that the authentication token is either expired or not being applied correctly in the request.

I noticed this issue had been addressed previously, but I wanted to check if the solution is still effective or if there have been any recent reports of similar occurrences. I’ll be running some tests on my end to observe the behavior, but I’d appreciate any insights or recommended troubleshooting steps in case the problem persists.

​@pirhyar34 

Since Jira is an external system, occasional issues may arise—especially when changes are made on Atlassian’s side.

If you notice an authorization issue with your integration, the first step is to reinitiate the integration to ensure your credentials are valid and up to date.

I faced the same error and was looking for solution. After reading different answers at this thread i got it. 

I’ve recently encountered a similar problem while working with the API integration. Occasionally, I’m getting a 401 Unauthorized response when attempting to perform certain operations, which usually points to issues with the authentication token—either it’s expired, malformed, or not being passed correctly in the header.

I understand this was discussed earlier in the thread, but I wanted to confirm whether the original solution is still effective or if others have noticed this resurfacing recently. I’ll continue testing on my end to rule out any local config issues, but I’d appreciate any updated insights or recommended troubleshooting steps in case the error persists.