Wait for linked request - does this work if used in a linked request?

[Adrian Simpkins]

Hiya,

We are making use of the new Wait for Linked Request node in our parent request, and this is working well for this scenario where you have a parent request, with linked requests. However, we have a requirement to raise a linked request dependent on correct criteria to raise a linked request. 

However, the wait for linked request node in the linked (now parent) request does not appear to be working the same. So I wanted to check should this work on a linked request raising another linked request? We have set the request number to be the newly created linked request from the outcome on the create linked request node, but it appears to just ignore the wait for linked request completion.

Many thanks as always

[Steve Giller]

2 minutes ago, Adrian Simpkins said:

We have set the request number to be the newly created linked request from the outcome on the create linked request node, but it appears to just ignore the wait for linked request completion.

Wait for Linked Request does not wait for a Linked Request to be completed, it waits until the current Request has another Request linked to it.

Are you using this node, or the Wait for Linked Requests Completion node?

[Adrian Simpkins]

Hi Steve, yes sorry wrong description of the node - using the Wait for Linked Request Completion in the parent request, and below is the flow in the linked request that needs to raise another linked request

Parent:

Linked request:

[Steve Giller]

33 minutes ago, Adrian Simpkins said:

We have set the request number to be the newly created linked request from the outcome on the create linked request node

I suspect that this is your issue, then - this should be the request that is suspended, not the request that you are waiting for.

[Adrian Simpkins]

Thank you Steve, I will replace that value, and try another test

 

[Adrian Simpkins]

Hi Steve, just a quick update: we could not get it to work with Wait for linked request completion node, but it is now working with a Wait for request update node instead.

Thank you as always