Calling Custom Events Consecutively

I tried to call the same custom event sequentially, 3 times. By the time the second one is called, it will stop execution of the first call. By the time the third one is called, it will stop execution of the second call. I thought custom events are run on a separate process thread? So why does the next call always cancel the previous call?
Is it supposed to be like this?

Hello Pelangi,

I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any blueprints/settings that may be involved with this issue?

Here you go. Notice that after 5 seconds, only “FINISH EVENT: 3” appear. The other 2 previous events were never completed.

After taking a quick look at the screen shot provided, this appears to be working as intended. The reason that you are only getting one print string after the 5 second delay is because all execution inputs are ignored while the delay is counting down. I have provided a screen shot of the tool tip below. I hope that this information helps.

Example:

Make it a great day

Hi Rudy. Maybe I expressed it the wrong way. The delay node was intended to show you that the other calls to a custom event was not executed until the end.

Why don’t you change the delay node, with some tasks that are different every time it is executed (maybe generate random number). But make sure that the task in the custom event does not complete until the next call (2nd call or 3rd call) to that custom event. You’ll understand what I mean.

I ran a few more tests. I have not noticed anything out of place. This appears to be working as intended. My results from the test above are as follows:

Order of events:

  1. Running Event: 1
  2. Running Event: 2
  3. Running Event: 3
  4. Delay for 5 seconds
  5. Finish Event: 3

Example:

122227-customeventhelp1.png

Delay 5 seconds

122228-customeventhelp2.png

As you can see in the example above, it runs through each call and then finishes with one final print string (due to the other executions being ignored). The reason that 3 prints out is because after the delay fires the current value of the integer being passed in was 3.