Based on the information provided in the knowledge sources, there are a few potential reasons why you might be encountering a 404 error when trying to access

/login/flows?id=xxx

, even if the flow ID was provided by Ory. Here are some possibilities: 1. Expired Flow: The login flow might have expired. Login flows typically have a limited lifespan, and if you try to access an expired flow, you'll receive a 404 error. 2. Incorrect API Endpoint: Make sure you're using the correct API endpoint. The error you're seeing is consistent with the standard Ory JSON API error format. 3. Flow Already Completed: If the flow has already been completed or used, it might no longer be accessible, resulting in a 404 error. 4. Tunnel Configuration: If you're using the Ory tunnel, ensure it's configured correctly. An issue in the tunnel setup could lead to 404 errors. 5. Permissions: There might be a permissions issue preventing access to the flow, although this would typically result in a 403 error rather than a 404. To troubleshoot this issue, you could try the following: 1. Check if you're using the most recent flow ID provided by Ory. 2. Ensure you're making the request immediately after receiving the flow ID to avoid expiration. 3. Verify that you're using the correct API endpoint and method for accessing the flow. 4. If you're using the Ory tunnel, double-check its configuration. If the issue persists, you may want to enable debug logging if possible, as this could provide more detailed information about why the resource cannot be located. For more detailed information on API responses and error handling, you can refer to the [Ory API Reference](https://www.ory.sh/docs/reference/api) and [Kratos API Reference](https://www.ory.sh/docs/kratos/reference/api).