"Failed to retrieve user"

[Nick Turner]

User names are no longer appearing on any software or service project. Whether it be a customer or backend user. It just says "Failed to Retrieve User" following by a user ID such as 5bb23f03ab2e976d0b642186

[Andy Heinzer · Accepted solution]

Hi Nick,

Sorry to hear about this problem.  We were experiencing an issue that was impacting some Atlassian Cloud customers around the time you created this question.

The issue has now been resolved.  For further details you can review this statuspage incident link of: https://jira-core.status.atlassian.com/incidents/gvjj0kt2frfn

Regards,

Andy

[Evan Favermann Eisert]

We're still seeing this issue today 7/3/19. 

"Failed to Retrieve User 5c5b4b56b287111683608562"

[Miguel Reimer]

We've had this issue ongoing for the last 10 days or so.

Usually only affects initial issue created email but viewing issue and subsequent emails are fine.

However a few minutes ago, all users starting showing failed to retrieve, only to resolve itself a few minutes after that.

Edit - Jira status is showing maintenance right now so that would explain the most recent issue, but not the ongoing initial email issue.

[Michael Bessolov]

I have a similar problem when receiving email notifications from Jira.

For example, multiple users make edits/transitions on some Jira ticket, and I receive email notifications for this ticket, some of these notifications will have the users' names, other won't. It varies, so in one email notification the same person can be named, in another email the same person can be "Failed to Retrieve User xxxx"

[Andy Heinzer]

Hi all, sorry for the delay, I was out last week. 

It appears there was another documented incident in the time frame you replied here.  You can see more details about this in https://jira-core.status.atlassian.com/incidents/d48c8jq2nsm1

This specifically affected user profiles and user searching.  So the given error certainly looks like it was directly related to this scheduled maintenance.  Sorry for the inconvenience.  I expect this has been resolved.  If not, please let me know.

Andy

[Leonard Krygsman]

Seeing this again today.

[Keenan Bernard]

Currently having similar issues

[Carole]

Hello I am still getting the "Failed to Retrieve user" issue.  It doesn't seem resolved. It's always happening with first time users who contact the JSD. Can you please advise? 

[Andy Heinzer]

Hi @Carole 

In your case, I would want to create a support case so that our Cloud Support team can take a closer look at your environment.  You can do this by

1. going to https://support.atlassian.com/contact/
2. Select Technical issues and bugs
3. Select Product (Jira)
4. Select Cloud
5. and enter your cloud URL (such as example.atlassian.net)

This will ensure that your request is routed to our technical support team that can more closely investigate this problem.

Thanks

Andy

[Nina Pyron]

We're seeing this today

[Puru Tharma]

I am experiencing this issue today for the last few days. 

[Andy Heinzer]

@Nina Pyron and @Puru Tharma Unfortunately,there is currently an active incident that is being tracked around this problem.  More details in https://jira-software.status.atlassian.com/incidents/mvpxzprry967

I would recommend subscribing to that event as this will be a quick way to get updates on this problem. Once resolved that incident will be updated to reflect this state.

Sorry again for the inconvenience here.

Andy

[Pamela Ross]

@Andy Heinzer We are seeing this error again today, "Failed to retrieve user" - is there a new issue to track?

[Andy Heinzer]

Hi @Pamela Ross 

I have not seen any outages that might involve this error recently.  Nor have I found any recent support cases about this error.  I would recommend creating a new support case by going to

1. https://support.atlassian.com/contact
2. Select Technical Support & bug reports
3. select Jira product
4. select Cloud
5. enter your Cloud URL

This will prompt you for more information, but will also submit your request to our Cloud support team that can better investigate your instance details.

[Karri Adkins]

 Happening here now too.  Very frustrating and causes confusion

[Emily Jarvis]

It's October and I'm seeing this again, please fix. I can't tell who is doing anything.

[Lacey]

Same here

[Donna Jorgensen Harrigan]

We are experiencing this issue as well.

[Mike Otto]

I've only encountered this briefly once before.
As of 5-10 minute ago I am seeing this issue across all projects.

[Emily Jarvis]

A follow-up. I can't see assignees, reporters, commentors, or even @mentions. We are desperate for a fix.

[Jessica Mosley]

We are experiencing this as well.

[Lil]

@Emily Jarvis , @Jessica Mosley , @Nick Turner :

I submitted a new ticket for this, if you wish to follow/ add your comments to it, to aid in faster resolution:

https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-522624

[zfinannee]

One of our users just asked me about this, and I've seen it this morning as well.   I would add a comment, but I do not have permission to view the request.

[Jennifer Eolin]

We are still seeing this issue as of 2:10pm EST, 10/22/2019.

[Lacey]

We are experiencing this issue widespread this morning...Was spotty previously...What is the cause and when will this be corrected?

[Jason Nowak]

Same as reported by Lacey. All users in tickets are showing "Failed to retrieve user" including when trying to @ tag someone internal to a ticket. ETA on resolution please. 

[Paul M_ Zahorosky]

I am seeing this issue as well. I cannot assign an issue to myself.

[Lil]

 I submitted a new ticket for this, if you wish to follow/ add your comments to it, to aid in faster resolution:

https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-522624

[Selena Moon]

We are also seeing this issue on and off today.

[Eric Fleet]

Same here...

[Allen Mikailian]

Same issue here.

[Tyler Sacre]

Same here

[Lil]

I submitted a new ticket for this, if you wish to follow/ add your comments to it, to aid in faster resolution:

https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-522624

[Rommel Caballero]

We are getting the same issue today.

[David Garrett]

We are getting the same issue today as well for coreljira.atlassian.net (Cloud Jira). We need this fixed ASAP. Note that https://jira-core.status.atlassian.com/ is now showing this error.

[katherine.mara.alinea]

Same issue with us today. Please help to fix. 

[Adam Dulberg]

Hello all on this thread - I'm not part of the Atlassian team, but figure to share that adding messages to a "Resolved" thread is not really best practice. Should be submitting help cases through their contact section and selecting the appropriate priority. Also, instead of duplicating a message from the person who wrote in right before you, might make sense to utilize the "Votes" shows on the left. If you're like me, reading this thread of the same messages from a mixed bag of dates is fairly confusing and not very helpful.

My point is, the more help requests they receive, more likely they are to ramp the priority and expedite a fix. I'm not so sure they value the quantity of community messages on a thread, less a resolved thread.

[Emily Jarvis]

Adam, 

Thank you for this, for the life of me I couldn't find where to submit this. I just created a ticket with them and put in a link to this thread. This has 34 people and counting that have been adding to it. Hopefully, they will see that.

[Michelle Cook]

Also having this issue at the moment. 

[Matt Leavitt]

It seems that this issue on October 21, 2019 has been resolved.  It is working again for us.

[Emily Jarvis]

FYI, it's spotty. It's been on and off all day. It might return.

[Lacey]

Ours is back and forth

[Matt Leavitt]

Ugh....  Would be nice if they actually reported an Incident at Jira Software or Jira Core for those who subscribe to those system errors (me).  Poor customer service.

[Arun Kumar]

We are currently facing the same issue !! 

[Gabriel Silverman]

Same issue for us too!

[Akira]

Same Here!

[Ramya Kalyanaraman]

Hello, We are experiencing "failed to retrieve users".

[Nathaniel Compton]

Is there an update on this issue?

[Selena Moon]

I created a ticket with Atlassian support for this issue by doing the following: 

1. going to https://support.atlassian.com/contact/
2. Select Technical issues and bugs
3. Select Product (Jira)
4. Select Cloud
5. and enter your cloud URL (such as example.atlassian.net)

I think the more reports here the the faster they will be at resolving this. 

[Lil]

I submitted a new ticket for this as well, if you wish to follow/ add your comments to it, to aid in faster resolution:

https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-522624

[Ujay A. Vincy]

Hey Lil, that's a support ticket we cannot access it. Nevertheless, it will get actioned from A's end.

[Jenniffer Guzman]

Este problema se esta presentando nuevamente hoy.

[Claudio Virginelli]

Here in Brazil we got the same issue today.
=S

[Zhenxi Mi]

We are experiencing the same issue right now.

[Zhenxi Mi]

the issue seems to be resolved on our end. Thanks for the fix!

[Crystal Varela]

We are also seeing this issue today. It was working just a few minutes ago. Is there a fix in the works?

[Ujay A. Vincy]

Hi there...

Just moments ago everything was fine and then user names are not showing up.

The issue seems to have re-cropped. Is there an ongoing incident? 

"Failed to Retrieve User 5d19feb5e3f1b90d1765bd47"

A quick help on this topic would be much appreciated.

Thank you.

[Ben Hart]

Same issue in our Org

[Ujay A. Vincy]

Hi Ben and Others....

The issue seems to have be rectified. Thanks to Atlassian team. Appreciated.

[Nylia Zamora]

We are still experiencing this on and off throughout the day. 

[Ramya Kalyanaraman]

Same issue for us from this morning.

[Andy the Drew]

We are experiencing this as well today - "failed to retrieve user".

[Ujay A. Vincy]

Yes, its on and off. But I am sure its not a problem. I saved a comment with the error message saying "Failed to Retrieve User 5d19feb5e3f1b90d1765bd47" but later it got updated properly to the referenced user.

In my opinion, there's nothing to worry much about this at the moment. when I '@' a user it still retrieves that user, error or not.

[Ujay A. Vincy]

Update: Haven't faced the user retrieval error today. All good.

[Thomas Schnitzler]

We are encountering the exact same problem sometimes since today.

[Pamela Ross]

We also are seeing "Failed to Retrieve User" again.

[Fernando Boucquez (PPL)]

I'm still seeing the "Failed to Retrieve User" in the rest responses. Is there any issue I can track?

[Deleted user]

I updated our workflow to a new one over the weekend. I made sure to map all existing Statuses to new ones. This morning, users are reporting an issue when moving existing issues into the Development status when we get the error in the Assigned and Project Manager fields:

Failed to retrieve user

I exported the user file and they are valid users who are not available in the drop-down lists  (since they are already assigned). 

Is this something that could have been caused by the workflow change? If so, what is the fix?

[miikhy]

Hi Nick,

This change in the user references is due to GDPR (the European regulation for privacy).

You can find more details here: https://www.atlassian.com/trust/privacy/gdpr

In most cases, APIs and functions allow you to retrieve user profiles with their unique ID, depending on what you're trying to achieve you should find a workaround!

Feel free to share more details if you need assistance porting your current state to a GDPR compliant way of working with Jira :)

Hope this helped!

Cheers

[Ujay A. Vincy]

Hi miikhy,

If it was GDPR related, why was it fine all these days and now suddenly I am facing the same error now?

I did not change my login credentials nor updated my profile in anyway in the recent past.