conductor
conductor copied to clipboard
Netflix
Conductor is a microservices orchestration engine.
We're seeing some behavior that looks like it could be some possible race condition when all tasks fail in a Fork, but no retries are ever attempted. We have 2...
Events for workflow completion and termination are currently published using the WorkflowStatusListener. These events can be used to trigger actions in downstream systems. However, if actions need to be triggered...
**Describe the bug** Creating a task where it is setup to retry upon failure, the retried task is populated with the previous failed attempt's outputData. **Details** Conductor version: 3.2.0 Workflow...
Conductor contains a large list of properties to customize its behavior. But these properties are scattered across several modules. There is not a consolidated place in the documentation where all...
**Describe the bug** RedisLockConfiguration.java in case of sentinel mode should accept multiple sentinel node addresses. Currently it takes in only one node address and discover other sentinel nodes by firing...
There is no redis password attribute in RedisProperties. Can't I set the redis password?
Currently, conductor treats all errors as one type and then increase the retry count if feasible to retry. In some use cases, users want to differentiate errors with different types...
### Discussed in https://github.com/Netflix/conductor/discussions/2333 Originally posted by **guru1306** June 24, 2021 Hi All We are using AMQP Message Queues to run our tasks with Dynomite as the backend. The queue...
With the release of Java 11, Nashorn is deprecated, and has been removed from JDK 15 onwards. The engine needs to be replaced with GraalVM. [Helpful article for migration](https://medium.com/graalvm/oracle-graalvm-announces-support-for-nashorn-migration-c04810d75c1f)
Conductor allows executing tasks in sequential order or in parallel using ( Fork or Dynamic Fork). However, the next task in a pipeline can only be scheduled once the previous...
