Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The multi-instance workflows executing occur "previous workflow execution scheduled different type of activity" #214

Closed
Robinmxc opened this issue Jun 27, 2023 · 3 comments
Labels
question Further information is requested

Comments

@Robinmxc
Copy link

Our application integrates workflow and is deployed with multiple instances. However, this error occurred recently.
image
image

I have read some of the source code and found that the generation of scheduleEventID may be the cause of this problem.

func (wf *WfState) GetNextScheduleEventID() int64 {
scheduleEventID := wf.scheduleEventID
wf.scheduleEventID++
return scheduleEventID
}

Because we are deploying multiple instances, it may not result in all scheduleEventIDs being generated within the same instance. Therefore, I would like to ask if workflow does not support multiple instances.

@cschleiden
Copy link
Owner

Only a single executor should work on a task and an instance at a time, so there shouldn't be any conflicts. All of the events having the same #420 sequence ID looks suspicious to me. What backend are you using?

@cschleiden cschleiden added the question Further information is requested label Jun 30, 2023
@Robinmxc
Copy link
Author

Robinmxc commented Jul 3, 2023

MySQL Server version: 8.0.32-0ubuntu0.20.04.2 (Ubuntu)
I guess this may not be a problem with the sequence ID. The sequence ID you see is the same, but it should be a problem with the front-end display. There is still a number after 420, so you may need to optimize the front-end display.

Here is another example, where there is a slight issue with the UI display.
image

@cschleiden
Copy link
Owner

Are you able to create a minimal repro or share relevant parts of your code?

@cschleiden cschleiden closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants