We are experimenting with knative sequences, we have defined a 3 step sequence similar to the one described in the knative tutorials : https://knative.dev/docs/eventing/flows/sequence/sequence-terminal/

We call the sequence using a POST cloudevent request that correctly triggers it. We use the sequence’s Address as a target (which resolves to the address of the sequence’s first channel). The POST request remains pending until the whole sequence is over (all steps), but the HTTP response we get is not the output of the sequence, instead we simply get :

{
    "body": "",
    "headers": {
        "allow": "POST, OPTIONS",
        "date": "Thu, 02 May 2024 13:20:00 GMT",
        "content-length": "0",
        "x-envoy-upstream-service-time": "24452",
        "server": "envoy"
    }
}

When adding a “reply” block, the sequence correctly sends the event to the described sink. In both cases (with or without reply) the caller of the sequence does not get the output of the sequence in return to his request. What bugs us is that the request remains pending until the whole sequence is over, so it seems logical that we should get the output of the sequence’s last step.

Is this a feature ? Or did we miss something in the configuration ?
Any help would be appreciated, thank you very much.