On my page when new user creating an account, he have message pops up: ‘‘this account already exists’’. And that’s not possible, because it’s a made up email for testing.
Do you know what could be the reason?
Was the made-up email for testing already used for testing?
You’ll get this error if the email is the email of a user in your database. You can delete that user or change its email to resolve this.
I’d be willing to bet a fair amount of money I know the reason…
2 Likes
First time used
What reason :)? please help
Hmm. If that email truly hasn’t been used before then I don’t know!
I’d be willing to bet a fair amount of money why he’s betting a fair amount of money is because he believes that the email is already a user in your database.
2 Likes
I would also be willing to bet a fair amount of Mac’s money that the reason Adam would bet a fair amount of his money is because he believes the email is already in use. 
Are you absolutely sure it’s not in your database?
3 Likes
2 Likes
What reason :)? please help
If you want to share a link to your editor (either here or in a DM), I’ll be happy to take a look…
I have two places to set up my account:
main: registration page - there is no this error
secondary: the place where you book a table - there is this error
I send you link in DM
Right… well I took a look at your editor, and it’s no surprise that the reason you’re seeing the error message “This email is already in use” is because…
wait for it…
… the email address is already in use!!
(i.e. there is already an account with that email address in your database).
So, somebody must owe me some money here…
However, the reason for this might not be so obvious to you, so I’ll explain what’s going wrong…
Basically, for some reason, you’ve got 2 workflow events (with the same ‘only when’ condition) running on the same button click (app text register), both of which are signing the user up (or trying to).
So the first one runs no problem, and signs the User up, then the second one tries to run and sign the User up with the same email address, but it fails as the email address is already being used by that point, hence why you get the error.
I don’t know why you’re running the same ‘Sign The User Up’ workflow action twice… but that’s the problem. So don’t do that.
2 Likes
setting up a recursive workflow…
2 Likes
Thank you 
I have had this set up for 5 months, the error has been popping up for 2days.
I enter an email e.g. bubbleforum@wp.pl - which is made up and there is an error.
I have two workflows because it’s quicker if someone chooses a booking date and doesn’t have an account yet, they can quickly set one up and complete the booking.
I’ll think about leaving just one - however, that’s not the reason for the bugs because it worked without problems for several months.
If this app has had the same set up for the last five months that it has now, there is NO WAY it has been working, as the current setup is simply wrong, and can’t possibly work.
If it’s only started doing this in the past 2 days, then you (or someone else) must have made the changes which have broken it.
(or the second workflow mysteriously appeared all by itself)
I enter an email e.g. bubbleforum@wp.pl - which is made up and there is an error.
Yes… of course there’s an error - your workflow doesn’t make any sense, and will always produce that error… I explained above why that’s the case.
I have two workflows because it’s quicker if someone chooses a booking date and doesn’t have an account yet, they can quickly set one up and complete the booking.
You can’t run 2 workflows at the same time to sign the User up with the same email address - it can’t possibly work.
I’ll think about leaving just one
Well, if you want to leave your app broken then, by all means, think about it.
But if you want to fix it then you MUST remove one of the workflows.
It’s simply a fact that you can’t sign 2 users up with the same email address (which is exactly what you’re current workflows are trying to do).
Whether you believe that or not is up to you.
however, that’s not the reason for the bugs
Yes it is… (although it’s not a bug - you’ve just built some workflows that don’t make any sense and will never work).
1 Like
Thank you very much for your commitment.
I leave one workflow.
Thank you very much for your help 
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.