Campaign or Fund Search Flow- Fails sometimes

Carol Grant

Hi all- I am using a great flow that was created by @Glen Hutson that allows users to search for Appeals, Funds or Campaigns. I wonder if anyone is currently using it and if they ever have it fail?

The flow was posted here in the community by Glen

The error message says the following:

The execution of template action 'Response' is failed: the client application timed out waiting for a response from service. This means that workflow took longer to respond than the alloted timeout value. The connection maintained between the client application and service will be closed and client application will get an HTTP status code 504 Gateway Timeout.

The flow works, it doesn't really fail. I do get reports saying it has an error up to 200 times. Is there anyway I can prevent this? Is this saying they have left the search open too long?

Thanks,

Carol

Glen Hutson

@Carol Grant
Is it failing out specifically for a certain type of search.. meaning always Funds, always Campains, always Appeals, or really just hit-and-miss?

Glen Hutson

@Glen Hutson:

@Carol Grant
Is it failing out specifically for a certain type of search.. meaning always Funds, always Campains, always Appeals, or really just hit-and-miss?

I missed the actual title of the message.. it's Friday…. The way the flows work is that it pre-loads every CFA first (depending on if it's the campaign, fund, or appeal instance) and then you can filter from there in the UI. So, if you have a “lot” (and I know that's a subjective term), then there may be the chance of it timing out as it's waiting for the list. May be worth some investigation on how to play around with timeout settings and/or another way to streamline.

The underlying Connector Actions don't have a lot by way of filtering, but it does have “Include Inactive” which is by default set to ‘No’. Understanding that when we're talking about policies, procedures, etc it may be easier said than done, but if you truely have CFAs you're not working with anymore, marking them as inactive (if not already) could help.

Carol Grant

@Glen Hutson- thanks! Where would I find the timeout settings? Under Time then Terminate after a certain delay?

Glen Hutson

@Carol Grant:

@Glen Hutson- thanks! Where would I find the timeout settings? Under Time then Terminate after a certain delay?

I'd open the flow and see if you can find which action specifically may be failing. Various actions have Timeout controls under the action settings (as in while in classic view, the 3 dots and then settings).

Alex Wong

@Carol Grant
I used Glen's AIO previously and had to make some change to it in order to avoid problems like yours.

The error you are having can be b/c of 2 situation:

1. As Glen mentioned, the flow fail to response back to the request. A HTTP flow requires the response to be provided within a set period of time (I think it's 2 minutes but not sure) and it is not configurable. If your flow did not finish it's “logic” (goes through all the actions prior to the Response action), the requesting client will get a timeout.
   1. Depending on what the flow does, Response DOES NOT hae to the last action in the flow. You can first response and do additional action as long as your response is not dependent on these action's dynamic content.
2. 2nd problem is when the flow is trying to response, but can't, b/c the user already nevigate away from the page and client is not receiving response anymore.
   1. in this situation, you have to do better error handling on the Response action, where it “failing” doesn't cause your flow to fail. (using a success terminate action after the response action with the terminate action configure to run after Response on success or fail

Carol Grant

@Alex Wong - thanks Alex, this is what I'm talking about! I realized it happens more with the Fund Relationship Tile (one of Glen's other AIO flows).

For #1, I think the Response does have some dynamic content so I may to watch some of your error handling demos to get some ideas for this one. For #2, I will look into adding an additional action for error handling like the Terminate action.

I'm glad to hear it wasn't just me!

-Carol