You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
Our application integrates workflow and is deployed with multiple instances. However, this error occurred recently.
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.
The text was updated successfully, but these errors were encountered: