Use the list created during backend workflow in the next step of backend workflow

When I press the button, the flow shown in the image is executed.

In step 3, use the schedule API workflow to create a list for w51m.
Also, in step 4, use the schedule API workflow to create a list of w51h.

In step 7, we use the lists created in steps 3 and 4 as keys to change the values ​​in the w51m list.

However, the STEP7 flow is not executed (the list value is not changed).

I think this is probably because STEP7 is executed before the flows of STEP3 and STEP4 are finished, but how should I set it so that STEP7 will be executed?

this is a common issue, you’re right, step 7 is most probably triggered before 3&4 are completed. Have you checked the debugger? did you try step-by-step?
if so, maybe you can add a small pause before step 7 and see what happens or maybe save the results of step 3&4 to two custom states and add a workflow with step 7 that runs only when the states 3&4 are not empty.

1 Like

Hanan1

Thank you for your reply.
Now that I know the cause, I tried adding a little pause before 7STEP.
But I can’t run it.
I tried setting the states method, but STEP 3 and STEP 4 are API workflows.
What kind of results can be set in a custom state?

Hi there,

Is it possible to add a field on the datatype created, ‘random’, and generate a random set of characters that is then set on all data created in steps 3 and 4, and then for step 7, add data with that same random characters?

1 Like

msgiblin san

Thanks your reply.
I’m afraid that I can’t understood your method using my brain…
Is there a simpler way to rewrite the data created in the previous step in the next step? (> _<)

I tried putting STEP3 and STEP4 in the custom event.
And put Step7 in another custom event.

But , can not run it.

depends on what your workflows returns, is it an object, text? that should be the state’s type

1 Like

everyone

Thank you very much for all your advices.

I have tried various methods of yours in my own way.

I tried to think of the custom state that everyone mentioned, but I just couldn’t set it( cause my brain is not enough).

We recognize that the problem is due to asynchronous processing, so we have changed the execution order as follows to ensure that the execution order is correct.

  1. Creating w51m and w51h tables
  2. Wait 5 seconds
  3. Popup display (trigger)
  4. When popup opens, change w51m table

Thank you very very much for all the advices.
Also, I’m sorry that I couldn’t meet your expectations.

You could put steps 3, 4 and 7 in a custom events that way they will execute before the rest of the actions.

“In a workflow with two actions, if Step 2 is using a condition based on a search depending on data manipulated in Step 1, then Step 1 should be implemented into a custom event to make sure it is finished before moving on to Step 2.
If a backend workflow should be triggered after other steps in the workflow, then it should be implemented in a custom event placed after the steps that need to come first.”

2 Likes

curran san

Thank you for your advice.
I’m thinking of implementing a custom event for 2STEP (STEP3 and STEP4) as well.

Thank you very much.

Hope it solves the issue! Let me know how you get on.