Error saving a flow: "Shape [Wait] does not support outgoing connectors of type Action"
I am creating a flow which will attempt to resend an SMS message to a customer in the event of a failure to send, after an interval of 1 hour. This is a BRE flow with no user intervention required or wanted, I just want it to wait for an hour and then resend, up to a configurable number of times. I am running Pega 07-10 ML9
The new Pega-7 'Wait' shape would seem to be ideal for this purpose, but it is impossible to insert into my flow as it does not appear to allow a connector to come out of it!!! Please see screenshot below.
Has anyone seen this problem, and does anyone know of a hotfix for it? Thanks.
I just created a test flow with a Wait shape and did not encounter any errors saving the flow. Can you show a screen shot of the properties for your Wait shape connector? I tested using the default pyContinueAfterWait action.
Please confirm you have “Draft” switched off – it saves Ok with draft on.
There is no way I can even add a connector with draft off. I have to turn draft on, then add the connector and save, then turn draft off to see the error.
There are no properties to the connector. I create the connector just by clicking the mouse on bottom of the shape, and dragging a line out to the next utility shape where I want the flow to go. And that’s it. No setting properties or calling DTs or anything.
On my PVS system and when I use the ‘PRPC:Administrators’ access group, then the connector that comes out of the ‘Wait’ shape is a flow action connector. Using my normal access group on the target customer’s cloud system I get only a vanilla connector without a flow action option. Clearly we have a configuration issue.
On Pega Mesh there is a post by Matt Broch about a workaround for a problem he was having with ‘Wait’ shape (search for “Wait for Timer Not Continuing”) and he used a standard Assignment with an SLA to ‘AdvanceFlow’, and the flow action he used was pyContinueAfterWait.
I have implemented the same solution, and it appears to work Ok. My revised flow is shown below. Thank you very much for taking the time to look at my problem, and provide your assistance.