# Log in workflow stops working after log out

**URL:** <https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090>\
**Category:** App Organization\
**Created:** [May 17, 2023, 2:14am UTC](https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090 "2023-05-17T02:14:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rschil95](https://avatars.discourse-cdn.com/v4/letter/r/aca169/32.png) [@rschil95](https://forum.bubble.io/u/rschil95)\
**Post date:** [May 17, 2023, 2:14am UTC](https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090/1 "2023-05-17T02:14:50Z")

</div>

Hey guys,

When I launch my log in page and sign in as a user all works well and all workflows trigger. If I log the user out and go to the log in page and sign back in, none of the work flows will trigger after “log user in” and pushes me to a white screen.

Even if I remove my custom event trigger and do a simple go to page, it still will not trigger that. Confirmed with the debugger that the workflow stops at this stage.

Any ideas?

 ![Screenshot 2023-05-16 at 10.08.47 PM](https://us1.discourse-cdn.com/bubble/original/3X/a/0/a0a8fdefd289f734244e0e2751b9eae1efdfaf97.png)  
 ![Screenshot 2023-05-16 at 10.09.39 PM](https://us1.discourse-cdn.com/bubble/original/3X/a/4/a47622ae3709a1e2f3562897c2a89a0803f179b6.png)

---

<div class="post-metadata">

**Author:** ![ranjit](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ranjit/32/254854_2.png) [@ranjit](https://forum.bubble.io/u/ranjit)\
**Post date:** [May 17, 2023, 5:14am UTC](https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090/2 "2023-05-17T05:14:46Z")

</div>

When you log out, the Current User thing changes from a user in your DB to an anonymous user with all the custom fields empty. Looks like the `signup_complete field is yes` part doesn’t evaluate to true.

---

<div class="post-metadata">

**Author:** ![rschil95](https://avatars.discourse-cdn.com/v4/letter/r/aca169/32.png) [@rschil95](https://forum.bubble.io/u/rschil95)\
**Post date:** [May 17, 2023, 1:46pm UTC](https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090/3 "2023-05-17T13:46:42Z")

</div>

Right that makes sense, but the user has re signed back in so Current User is the user who just logged in?

---

<div class="post-metadata">

**Author:** ![ranjit](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ranjit/32/254854_2.png) [@ranjit](https://forum.bubble.io/u/ranjit)\
**Post date:** [May 18, 2023, 3:52am UTC](https://forum.bubble.io/t/log-in-workflow-stops-working-after-log-out/263090/4 "2023-05-18T03:52:45Z")

</div>

Not according to this condition.  
It’s not tied to the condition that the user must be logged in.  
You could modify it to be something like `signup_complete field is yes and current user is logged in`.

Alternatively, if this is supposed to trigger when the user logs in, I’d change the condition of the workflow to `current user is logged in` and add the `signup_complete field is yes` condition to the `go to page` action within the workflow. This will also trigger when the page loads here and the user is logged in though.