APP-1039 flow-mismatch error raised for applications with no recovery/registration flows configured.

[KaveeshaPiumini]

Description

When creating or updating an application whose authentication flow contains a CALL node into a registration (or recovery) flow, the server silently auto-fills the app's registrationFlowId/recoveryFlowId from that call target, even though the user never enabled or configured a registration/recovery flow. A later update then fails with a confusing APP-1039 "Conflicting flow references" error that references a flow the user was never aware they had.

{
    "code": "APP-1039",
    "message": {
        "key": "error.applicationservice.application_flow_mismatch",
        "defaultValue": "Conflicting flow references"
    },
    "description": {
        "key": "error.applicationservice.application_flow_mismatch_description",
        "defaultValue": "The authentication flow references a different registration flow than the one configured on the application. Both must point to the same registration flow.",
        "params": { "flowType": "registration", "sourceFlowType": "authentication" }
    }
}

The message claims the app has a registration flow configured that differs from the one the auth flow calls, but the user never configured any registration flow. This makes the error impossible to act on.

Steps to Reproduce

1. Create an application and set only an authentication flow whose graph includes a CALL node targeting registration flow A. Leave the registration and recovery flows unset/disabled on the application. (Ex: can use console application)

2. Change the authentication flow and save the application changes.

Untitled.1.mp4

Version

v1.0.0-alpha

Environment Details (with versions)

No response

[ThaminduDilshan]

Even though it appears as no recovery/registration flows configured, if you just enable the registration/ recovery toggle, you can see a registration/ recovery flow is still set for the application. Hence the backend error is correct for this scenario as the authentication flow has a link to a different registration flow and the application actually references a different flow.

However I agree we should improve UX around this. IMO we can prevent hiding flow configuration section even when the toggle is disabled. Instead we can show it in a disabled state where it doesn't allow to change related flow configuration.