# Users unable to login to production app

**URL:** <https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919>\
**Category:** Need help\
**Created:** [June 8, 2021, 11:13pm UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919 "2021-06-08T23:13:06Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 8, 2021, 11:13pm UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/1 "2021-06-08T23:13:07Z")

</div>

Hi,

Is anyone experiencing issues with their app?

My users are unable to login to existing accounts.

Message on login - Sorry, we ran into a temporary bug and can’t complete your request. We’ll fix it as soon as we can; please try again in a bit!

Thanks  
Robbie

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 12:06am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/2 "2021-06-09T00:06:50Z")

</div>

Hey 👋 @stuart.leo

I’m on a personal plan on mine and I can log in just fine. I don’t have a higher tier production app though. So not sure if this helps you.

Still having the issue?

Hope that helps! 😊

@j805 [www.NoCodeMinute.com](http://www.nocodeminute.com/)

For All Your No-Code Education Needs:

- One-on-One Tutoring
- eLearning Hub
- Video Tutorials

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 12:09am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/3 "2021-06-09T00:09:03Z")

</div>

Yep, we’re on the professional plan with paying users unable to login.

Looks like a server issue.

Backend is fine and new sign ups are able to login and access the app but existing users are unable to login.

I’m based in Australia and Bubble support seems to only work US office hours…

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 12:12am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/4 "2021-06-09T00:12:08Z")

</div>

Yeah. Hmm 🤔 Make sure your report says production app completely broken, I think they monitor it for emergencies.

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 12:20am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/5 "2021-06-09T00:20:03Z")

</div>

Thanks @J805 I did that about an hour ago but still no response…

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 12:24am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/6 "2021-06-09T00:24:26Z")

</div>

If you can, push to live and see if that helps. Sometimes a bad update can break things. 🤷🏻‍♂️

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 12:44am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/7 "2021-06-09T00:44:02Z")

</div>

Another thing to check. What does your login workflow look like?

Random thought….Is there anything to do with location data?

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 12:48am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/8 "2021-06-09T00:48:48Z")

</div>

No, nothing related to location in login workflow.

1 user has managed to login.

I haven’t been able to push to live yet as I don’t want to kick them out in case they can’t get back in…

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 12:50am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/9 "2021-06-09T00:50:17Z")

</div>

Can you send a screenshot of your login workflow?

Are users already logged in and they are trying to log in again? Maybe add something on the page that skips the log in page if they are already logged in. Maybe that is the issue?

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 12:55am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/10 "2021-06-09T00:55:26Z")

</div>

Nothing has changed with my login workflow since it was built last year and has always worked fine.

I have just pushed to live and no change. I still get the same error message.

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 12:57am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/11 "2021-06-09T00:57:20Z")

</div>

Login workflow

 ![Screen Shot 2021-06-09 at 10.56.17 am](https://us1.discourse-cdn.com/bubble/original/3X/9/a/9a2eb0192315aa7a2dcc332b67095d17a781b475.png)

Active User  
 ![Screen Shot 2021-06-09 at 10.56.27 am](https://us1.discourse-cdn.com/bubble/original/3X/0/b/0b59c3ebdf43f4b6abb64b18614b1d6163f1fdf7.png)

Log out inactive user  
 ![Screen Shot 2021-06-09 at 10.56.32 am](https://us1.discourse-cdn.com/bubble/original/3X/1/0/101bba3df3672e07a5a554768e297f7e2b6d9a37.png)

User inactive

 ![Screen Shot 2021-06-09 at 10.56.39 am](https://us1.discourse-cdn.com/bubble/original/3X/6/f/6fd86f69361a09454d791d779f8858099e14f936.png)

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 1:04am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/12 "2021-06-09T01:04:09Z")

</div>

@stuart.leo

What does the log the user in step look like?

Also, for testing purposes, I would disable this workflow and make a very simple login workflow and test that to pinpoint which step is making it break. Add one step back at a time until it breaks. Then you know which one is causing the issue.

I would also recommend sending what you can to a backend workflow if possible, so if it breaks, it doesn’t interrupt the users flow. Like the send an event to mix panel step.

My first test would be to just have step 1 -login, step 2 - go to page. See if that works properly.

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 1:05am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/13 "2021-06-09T01:05:45Z")

</div>

Let me know if that works.

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 1:09am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/14 "2021-06-09T01:09:41Z")

</div>

Hi Jason, thanks!

Just turned off the login workflow and added a very simple one and worked fine.

Argghhhhhh

I was reading that it may have something to do with api calls timing out… any idea?

---

<div class="post-metadata">

**Author:** ![J805](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/j805/32/41267_2.png) [@J805](https://forum.bubble.io/u/J805)\
**Post date:** [June 9, 2021, 1:16am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/15 "2021-06-09T01:16:01Z")

</div>

Cool. Glad it worked. 👍😊

It very well could be an issue with one of your api calls. Maybe an API did an update. That could break a workflow. Once you have isolated which step causes the issue, then you can contact the API support and see if anything has changed or something.

You can keep adding each step back one by one until the error happens again to isolate it. It might show up in a step-by-step potentially too. Either way should work.

If you put these workflows on the backend, this will help to not have these issues in the future. The users won’t be affected if the call is done on the backend workflow.

Glad you got it working at least! 😊

@j805 [www.NoCodeMinute.com](http://www.nocodeminute.com/)

For All Your No-Code Education Needs:

- One-on-One Tutoring
- eLearning Hub
- Video Tutorials

---

<div class="post-metadata">

**Author:** ![stuart.leo](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stuart.leo](https://forum.bubble.io/u/stuart.leo)\
**Post date:** [June 9, 2021, 1:20am UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/16 "2021-06-09T01:20:44Z")

</div>

Yep, thank you for you help, in to the step by step testing now!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [August 17, 2021, 11:13pm UTC](https://forum.bubble.io/t/users-unable-to-login-to-production-app/154919/17 "2021-08-17T23:13:44Z")

</div>

This topic was automatically closed after 70 days. New replies are no longer allowed.
