Aravindan Ramkumar

@v1r3n The tests are fixed. You can rebase from main

@JamieSlome Thanks for reaching out, please check, https://github.com/Netflix/conductor/security/policy

> If there is a need to use output data from the failed attempts, it would be possible to cycle through the failed attempts get that info but if we...

@csharplus this is a good first issue to look into, if you are interested.

@kartaa mysql is a community contributed module and looks like the original contributors are not active in maintaining the module. This issue is not actively looked into.

@lianjunwei based on the screenshot in your initial question, `conductor.client.rootUri=10.190.32.157:8080`. You have configured the client to poll from only one instance of your cluster. Please ensure that both instances point...

@fscorro The call returns a `417` status code. Its not a successful response and thats why Conductor throws an exception. Am i missing something?

@ZergRushJoe Please do. Appreciate the help. the docs need some love.

@duoertai @csharplus this is another issue that you can look into.

The internal queue is managed by [ConductorEventQueueProvider](https://github.com/Netflix/conductor/blob/main/core/src/main/java/com/netflix/conductor/core/events/queue/ConductorEventQueueProvider.java) and [ConductorObservableQueue](https://github.com/Netflix/conductor/blob/main/core/src/main/java/com/netflix/conductor/core/events/queue/ConductorObservableQueue.java). The `ConductorObservableQueue` could be loaded using `EventQueues.getQueue()` method. > Just want to check if I understand this issue correctly, to publish...