Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Releases: Netflix/conductor

Merged from dev, added metadata to failed workflow

18 Dec 21:27
Compare
Choose a tag to compare
v1.8.2-rc5

Merge branch 'dev'

1.8.2-rc4

18 Oct 16:43
Compare
Choose a tag to compare
1.8.2-rc4 Pre-release
Pre-release

Fixed Response timeout issue

1.8.2-rc3

12 Oct 19:51
Compare
Choose a tag to compare
1.8.2-rc3 Pre-release
Pre-release
Merge pull request #345 from Netflix/dev

Dev

1.8.2-rc2

06 Oct 20:54
Compare
Choose a tag to compare
1.8.2-rc2 Pre-release
Pre-release
Added API to reset task callback timeouts to 0 (Part 2)

1.8.2-rc1

22 Sep 15:17
Compare
Choose a tag to compare
1.8.2-rc1 Pre-release
Pre-release

Fix the issue with response timeout.

1.8.1

17 Sep 16:47
Compare
Choose a tag to compare
  • Add polling throttle in the client side when execution queue is full
  • Fix a bug with retries where the retried task does not correctly replace the taskId of the current task (and instead uses the id of the previous task)
  • Pin dyno-jedis to 1.5.9
  • Address timeouts when using redis cluster on aws elasticache
  • Allow overriding the thread-name in the java worker client

1.8.0

11 Aug 22:13
Compare
Choose a tag to compare

Bug Fixes

  • Fix the rerun bug when sub workflows are involved
  • Fix for retry with fork join workflows

1.7.6

20 Jun 18:28
Compare
Choose a tag to compare

New Features

  • Task Execution Logging API
    ** Allows logging additional information from workers. Worker can add additional logging details as part of the result that helps with debugging / understanding the execution context. The logs are shown in the UI

Bug Fixes

  • Fixes a bug with WAIT task introduced in 1.7.5

1.7.6-rc2

16 Jun 23:58
Compare
Choose a tag to compare
1.7.6-rc2 Pre-release
Pre-release
Merge pull request #225 from Netflix/dev

Task Logger Implementation for the worker

1.7.5

06 Jun 18:14
Compare
Choose a tag to compare

Support For Task Domain

Task domains helps support task development. The idea is same “task definition” can be implemented in different “domains”. A domain is some arbitrary name that the developer controls. So when the workflow is started, the caller can specify, out of all the tasks in the workflow, which tasks need to run in a specific domain, this domain is then used to poll for task on the client side to execute it.