Fix flow expired error messages
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 187
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Ory Network Project
No response
Describe the bug
Whenever a flow expires, we show a pretty specific error message, including the time of expiring or duration since expiry.
Instead, we should a more generic error message, or silently retry the interaction in the back.
Note, this is probably also a Kratos issue.
Reproducing the bug
- let flow expire
- try to interact with the flow
Relevant log output
Relevant configuration
Version
master
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the expired-flow interaction described in the issue, then trace where Ory Elements renders the expiry error and determine whether the message comes from Kratos. Done should mean agreeing on either a generic message or silent retry and verifying that expired flows no longer expose specific timing details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100