Jeff Bull

👋 **Hi** @ravig-kant @aradu-atlassian We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed. **To help us keep the backlog focused and...

@maggmanu77 based on @v1r3n comment above regarding PR #221 has this issue been resolved?

👋 **Hi** @sunwuxiang We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed. **To help us keep the backlog focused and actionable,...

Assigned to @bradyyie as an enhancement for an upcoming release.

👋 **Hi** @arorashivam @lbestatlas We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed. **To help us keep the backlog focused and...

> Agreed the `MaxPostponeDurationSeconds` setting added in [v3.21.12](https://github.com/conductor-oss/conductor/releases/tag/v3.21.12) does mitigate the issue. Thanks @lbestatlas I'll go ahead and close this issue.

👋 **Hi** @Jiehong We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed. **To help us keep the backlog focused and actionable,...

> The code linked has not changed since then, so the behaviour probably hasn't either (can't test with latest conductor version at the moment). > > Thinking about it again,...

> Added/Updated project readme files [#271](https://github.com/conductor-oss/conductor/pull/271) @jmigueprieto has this issue been resolved?

@vishal079 @hexxone @tditz Sorry for the delay. I've brought this up with our conductor dev team.