Flow hook does not execute in the flow trace

[anonymous]

Hi there, hoping somebody can share some insights into Flow Hooks…

I currently have a Shared Flow which uses the AssignMessage Policy to remove/set some headers.

SharedFlow:

<SharedFlow name="default">
    <Step>
        <Name>Assign.ResponseHeaders</Name>
    </Step> </SharedFlow>

AssignMessage Policy:

<AssignMessage continueOnError="false" enabled="true" name="Assign.ResponseHeaders">
    <DisplayName>Assign.ResponseHeaders</DisplayName>
    <Properties/>
    <Set>
        <Headers>
            <Header name="X-Custom-Header">HeaderValueTest</Header>
        </Headers>
    </Set>
    <Remove>
        <Headers>
            <Header name="WWW-Authenticate"/>
        </Headers>
    </Remove>
    <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
    <AssignTo createNew="false" transport="http"/>
</AssignMessage>

This Shared Flow has then been deployed to all environments.

Next, I then attached this Shared Flow to the “Post-target Flow Hook” and “Post-proxy Flow Hook” items in all environments.

When I go to trace any API Proxy in an environment, I don’t see the Flow Hook Steps being executed and the Header modifications have not occurred.

I’m wondering if there is anything I have missed?

Cheers

[anonymous]

To follow on from this, I just unselected the Shared Flows from the Flow Hooks and hit Save. Now if I try to Edit the Flow Hooks and add them back in, the list is empty? All shared flows are deployed to the selected environment.

Flow Hook List:

Shared Flow List:

[anilsr]

@Andre Johansson-Walder , Welcome to Apigee Community !

I am unable to reproduce above behavior, It works as expected & i can see the flow hooks getting executed as per the configuration.

See trace screenshot below that confirms same.

API call that you can test, http://apigee4mv4d-test.apigee.net/httpbin

Are you sure you have configured the flow hooks in right environments & testing same in the configured environment ? Also, I am unable to reproduce “list is empty” issue.

It might be your org specific, Please follow up with support since we are unable to reproduce here in community.

[anonymous]

Thanks @Anil Sagar

I do agree, I think this is org specific as the configuration steps we followed are identical.

I have raised a support case and will follow up there

Thanks again

[anonymous]

Hi @Andre Johansson-Walder,

Is this fixed for your org? I am facing similar issue in my org.

Thanks

[anonymous]

Hey - I don’t recall the exact fix, but I think it was just a message processor restart. (Hadn’t loaded the config change for some reason)

Cheers

[anonymous]

Thanks @Andre Johansson-Walder