Based on the provided knowledge sources, it is not possible to extend the duration of a login flow without changing the lifespan in the configuration file. The login flow has an expiration time (

expires_at

), and once it expires, a new flow must be initiated. There is no documented API or method to extend an individual login flow's duration dynamically; the only way to change the duration is by updating the configuration value for the login flow lifespan. If a user encounters an expired login flow, the recommended approach is to start a new flow. This is also reflected in user and maintainer discussions, where the expectation is that expired flows require re-initiation, and there is no mention of a mechanism to extend an existing flow's duration outside of configuration changes [Session lifespan](https://www.ory.sh/docs/kratos/session-management/session-lifespan) [Github Issue: login flow expired error](https://github.com/ory/network/issues/417). If you need a longer or shorter login flow duration, you must update the configuration and redeploy or reload the service as appropriate. There is no per-flow override or extension mechanism documented.