dill

> > Yes, I hope that I don’t need to frequently switch online operations during debugging, and I can release it to production after debugging is completed. > > In...

新增esreader，kafkareader插件

We also encountered this issue in practical use. It can be resolved by introducing a time period type, such as anyDayLastMonth, ensuring that downstream dependent tasks can function properly as...

@SbloodyS @ruanwenjun Help to see if it is feasible to make changes to the dependency cycle type?

> > Add several types："anyTimeToday,anyTimeLast1Days,anyTimeLast2Days,anyTimeLast3Days,anyTimeLast7Days,anyTimeThisWeek,anyTimeLastWeek,anyTimeThisMonth,anyTimeLastMonth" > > Add a parameter in calculateResultForTasks to determine if the task execution result is "any time in a period of time". If any workflow...

Could you let me know if this approach looks good? @SbloodyS @ruanwenjun add a checkMode field to differentiate between “ANY_SUCCESS” and “ALL_SUCCESS” requirements while maintaining backward compatibility. Behavior Examples: dateValue...

Please help review the code @wing2fly @amitsrivastava @ranade1

Hi @wing2fly @ramprasadagarwal @tabraiz12 @Harshg999 , the PR has passed all checks and reviews. Could you please approve the required workflows so it can be merged? Thanks!

@quadoss @ranade1 I've fixed the code formatting issue that caused the CI failure. Could you please review when you have time? Also, could you trigger the CI pipeline? Thanks!

Hi @F7kyyy I tried to reproduce the issue but was unsuccessful. In complement mode, when running workflow A, the downstream workflows B1 and B2 are not triggered. What specific configuration...