{"full_name":"cadence-workflow/cadence","owner":"cadence-workflow","name":"cadence","shard":"1","url":"https://github.com/cadence-workflow/cadence","description":"Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.","homepage":"https://cadenceworkflow.io","topics":["uber","cadence","workflows","orchestration-engine","workflow-automation","distributed-systems","service-bus","service-fabric","services-platform","golang","java"],"tag_pages":["distributed-systems","golang","java","workflow-automation","workflows"],"language":"Go","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/187651631?v=4","created_at":"2017-02-21T16:10:18Z","pushed_at":"2026-11-15T17:28:35Z","metrics":{"stars":9556,"forks":931,"watchers":1410,"issues":1692,"prs":6916,"releases":106,"issues_open":156,"issues_closed":1536,"prs_open":69,"prs_closed":863,"prs_merged":5984,"discussions":100},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[9546,9547,9548,9548,9555,9556,9556],"forks":[929,929,929,929,929,931,931],"watchers":[null,1411,1411,1410,1410,1410,1410],"issues_open":[null,156,157,157,156,155,156],"prs_open":[null,70,71,69,68,67,69]},"boards":{},"same_owner":[],"issues":[{"number":7830,"title":"Guided Cadence install mission in KubeStellar Console","comments":14,"created_at":"2026-03-18T15:45:27Z"},{"number":3914,"title":"Proposal: Reset to a reset point with pending ChildWorkflows","comments":13,"created_at":"2021-01-22T05:18:04Z"},{"number":348,"title":"Feature request: Provide http interface for activity workers","comments":10,"created_at":"2017-09-12T05:04:52Z"},{"number":7195,"title":"Add domain created_time value to DescribeDomainResponse","comments":8,"created_at":"2025-08-20T23:35:37Z"},{"number":4520,"title":"OAuth public/private key concerns","comments":8,"created_at":"2021-09-29T10:40:05Z"},{"number":7643,"title":"Refactor ExecutionManager/ExecutionStore to be a host-level component","comments":7,"created_at":"2026-01-23T20:52:01Z"},{"number":2403,"title":"Concurrency control of inflight workflows","comments":7,"created_at":"2019-08-16T21:57:30Z"},{"number":6706,"title":"Role based Cadence-web","comments":6,"created_at":"2025-03-03T17:03:00Z"}],"discussions":[{"number":7706,"title":"Client Request Auto-Forwarding","comments":0,"category":"Ideas","created_at":"2026-02-13T20:51:22Z"},{"number":7508,"title":"RBAC in the Cadence Web","comments":4,"category":"Ideas","created_at":"2025-12-05T12:05:37Z"},{"number":6888,"title":"Reporting scam emails","comments":1,"category":"Q&A","created_at":"2025-05-06T14:36:11Z"},{"number":6633,"title":"delaystart seems not working when adding to the workflow option","comments":4,"category":"Q&A","created_at":"2025-01-17T20:03:10Z"},{"number":6372,"title":"Upgrade cadence mysql db only?","comments":2,"category":"General","created_at":"2024-10-16T19:13:59Z"},{"number":6269,"title":"history_node table is taking too much storage [database: postgres]","comments":1,"category":"Q&A","created_at":"2024-09-06T13:54:39Z"},{"number":6024,"title":"When can we expect the official helm charts to be released?","comments":1,"category":"General","created_at":"2024-05-15T04:57:29Z"},{"number":5958,"title":"Can anyone please help with the monitoring params that needs to be taken into account","comments":1,"category":"Q&A","created_at":"2024-04-30T05:13:18Z"}],"latest_release":{"name":"v1.4.5","tag":"v1.4.5","published_at":"2026-10-30T22:16:09Z","body":"## Upgrade Notes\r\n\r\n- Cassandra schema: apply migrations through `v0.55` before rollout (current is `v0.52` in v1.4.2). `v0.53` adds the `semaphore_info` type and `executions.semaphore_map`, `v0.54` adds `jitter_coefficient` to `workflow_execution` and `activity_info`, and `v0.55` adds `semaphore_name` to `transfer_task`. MySQL, PostgreSQL and SQLite schemas are unchanged. Schema updates that fail partway can now be re-run: duplicate DDL statements are logged and skipped (#8598).\r\n- If you're on a version older than v1.4.2, deploy v1.4.2 first, since it carries the read filter the tombstone reduction depends on. See Cassandra Tombstone Reduction below.\r\n- Default changes. These are on after upgrade unless you set them explicitly:\r\n  - `history.enableTimerQueueV2` and `history.enableTransferQueueV2` now default to `true` (#8617).\r\n  - `history.timerProcessorCachedQueueReaderMode` and `history.transferProcessorCachedQueueReaderMode` now default to `enabled` (#8565, #8592). In v1.4.2 both defaulted to `disabled`. Set `disabled` or `shadow` to go back.\r\n- `FailoverDomain` is now only accepted at the destination cluster (#8542). A request is rejected unless every target cluster it names is the cluster that received it. Scripts or tooling that fail a domain over from another cluster must pass `--skip_destination_check` (CLI, #8540) or set `SkipDestinationClusterCheck` on the request (#8539). The V2 failover workflows forward the flag (#8541). `UpdateDomain`-driven failovers are unchanged.\r\n- The server now refuses to start if the configured dynamic config client cannot be initialised (#8670, #8619). A syntax error, a missing file, an unreachable config store or a typo in `dynamicconfig.client` used to fall back to the no-op client and silently run on defaults. The no-op client is now used only when dynamic config is not configured, or when `dynamicconfig.client: nop` is set. Validate your dynamic config before upgrading.\r\n- Metrics: the `workflow_execution_history_access` gauge was replaced by the `workflow_query_age_days` histogram (#8559, #8566). Queue v2 cache metrics lost their `shard_id` tag and `cached_queue_prefetch_window_span_ns` was removed (#8551).\r\n- Go module language level is now 1.26.0 with toolchain Go 1.26.9 (#8675). Build environments must provide Go 1.26 or allow toolchain download.\r\n- `v1.4.3` and `v1.4.4` were tagged by mistake and have been removed. If you already have one of those tags, it is this same commit. v1.4.5 is the release to install.\r\n\r\n## Major Features\r\n\r\n### 1. Cassandra Tombstone Reduction ([#8318](https://github.com/cadence-workflow/cadence/issues/8318))\r\n\r\nCassandra creates a tombstone for every key-value deletion on a map column. Cadence tracks pending activities and pending timers in map columns, so every activity completion and every timer firing created one. Together with the read filter and unset-value work in v1.4.2, this release adds the write path for #8318: batch map deletion writes (#8522).\r\n\r\nWhen enabled, deleting a pending activity or timer entry writes a sentinel value (`activitySentinelScheduleID`, `timerSentinelTimerID`) instead of issuing a delete. To keep the collections from filling with sentinels, a transaction that contains deletes will, with probability 1 in N, rewrite the whole pending activity or timer collection and drop the accumulated sentinels. Readers filter sentinels on load, so they are invisible to workflow logic.\r\n\r\nThis release also exposes Cassandra server warnings, such as tombstone overload on a read, from the persistence layer (#8678). It is groundwork for cleanup workflows that read, check, and skip the delete when a read hit too many tombstones.\r\n\r\n#### Configuration\r\n- `history.rewriteSampleRate` (default `0`, disabled): N means a roughly 1-in-N chance per transaction with deletes. `0` keeps the previous delete behaviour. `1` rewrites every time. The setting is dynamic and acts as the kill switch. A larger N means fewer rewrites, so more sentinels accumu","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}