You're paying your developer to ask questions instead of building.
Every unclear ticket turns into follow-up questions. Those are billable hours. MurMur is an agent that knows your project and helps you write tickets your developer can build on the first try.
Join waitlist now
ss1/Work items/#2001Broken login
The login is broken. I can't access my account because the login code does't work
Assignee
Labels
Priority
← Before MurMur
ss1/Work items/#20012FA verification fails to move users from Login to Authenticated (regression in v2.4)
Summary
2FA verification: entering a valid code returns the user to the login screen instead of signing them in.
Clarified with client
- Fails at the verification step, after credentials are accepted.
- Regression: worked before the last release.
- Reproduced on two accounts, so not account-specific.
Steps to Reproduce
- Log in with a valid email and password.
- Enter the 6-digit verification code on the following screen.
- Click “Verify.”
Expected Result
Per the authentication flow diagram, a valid code should move the user from “Pending Verification” to “Authenticated” state and load the dashboard.
Actual Result
The user is returned to “Login” state instead of “Authenticated,” with no error shown.
Project context (from documentation)
- Auth flow diagram shows three states: Login → Pending Verification → Authenticated. The break is happening on the second transition.
- Verification codes are valid for a 30-second window; the pending login itself times out after 5 minutes (per the auth spec).
- Release notes v2.4 list “updated session persistence settings” as a change — no other auth-related changes are listed for this release.
- User manual states verification should be a single step with no more than one retry needed for a valid code.
Acceptance criteria
- A valid code moves the user to “Authenticated” and keeps them there across Chrome, Firefox, and Safari.
- An invalid or expired code shows an error message and keeps the user on the verification step, per the user manual’s retry behavior.
- The verify step never silently returns to “Login” state.
Developer notes
- The v2.4 session persistence change is the most likely starting point, since no other auth-related change is listed for that release.
- Confirm whether the break is state transition logic itself, or session persistence after a correct transition.
- Check whether the 5-minute pending-login timeout could be expiring before verification completes for any of the reproduction cases.
Assignee
Labels
Priority
After MurMur →
Where the hours go.
You paid for
40 hrs
Ticket goes out,
questions come back
5 wasted hrs,
0 lines of code
Your developer needs to know the where, what, how, why and so on. Questions that cost hours which cost money and require knowledge that isn’t your responsibility. The chain of questions is avoidable, the clarity before development is not.
MurMur is your developer whisperer: an agent which learns your project. You describe what you want in plain words, and it asks the questions your developer would ask. You get a ticket that has everything needed to start building right away.
See for yourself
We're all about creating an effective, simple and agile experience, but don't take my word for it - play the video to see MurMur in action.
What's in it for you?
MurMur
can help you at any level of your expertise
Hey, login isn’t working. I need someone to check the code.
What actually happens when someone tries — do they see an error message, does the page just reload, or does it spin and do nothing?
One of my teammates said it just sends them back to the login page. No message.
Is this happening to everyone, or only some people — like certain team members, or people signing in a specific way?
At least two people today. Not sure who else.
Did anything change recently — an update or release — around when this started?
We did push something yesterday afternoon, now that you mention it.
One more — were they blocked right away, or did they get in fine and then get signed out a bit later?
Actually, one person said they WERE in for a bit, then got dropped back to login.
That’s really helpful. Ticket’s ready with everything laid out, including the likely cause. Review it and hit Submit.
Whether you're just getting started
Or if you already know your way around
I want to set up automated batch notifications — send a report by email to a list of people, with a few attachments included.
Who’s on the list, and what should the email say — fixed copy, or a template?
Pull from our existing distribution list; use the standard template, subject is just the report name and date.
Got it. What’s the max attachment size per email, and should we block anything over that or compress it?
Cap it at 10MB, just block it if it’s bigger.
Should these send at a fixed time each day, or right when the batch finishes?
Same time every day — 8am.
Last one — if a send fails for someone, retry, skip and continue, or stop the whole batch?
Skip and continue, but flag it so we know.
Perfect — ticket’s ready with everything specified. Review it and hit Submit.
Join the waitlist now!
Two quick questions, then you're on the list.