Files
Lina JodoinandGitHub 8c491ac98e [Scheduling] Add RunningWorkflows to schedule memos in visibility, and in ListSchedules results (#6665)
# What changed?
- **See the [API PR](https://github.com/temporalio/api/pull/464)**
- The `RunningWorkflows` field on a scheduler workflow's memo is now
copied into visibility with the rest of the memo.
- `ListSchedules` now returns `RunningWorkflows` in its resulting
`ScheduleListInfo` entries

## Why?
- Customers would like to be able to drill down into running workflow
executions without having to follow a `ListSchedule` call with fan-outs
to `DescribeSchedule`).
- We store `RunningWorkflows` alongside the rest of the memo so we can
return it efficiently as part of list queries

## How did you test it?
- New test: `go test -v ./tests -run
ScheduleFunctionalSuite/TestListSchedulesReturnsRunningWorkflows`
- New replay test `replay_recent_actions_includes_status.json.gz`,
generated with this branch
- ran new replay test on this branch, and main branch, with `go test -v
service/worker/scheduler/replay_test.go -run TestReplays`

## Potential risks
- We're pushing more data to the visibility store. In most cases, this
will be the size of a single `WorkflowExecution` struct, but there may
be multiple in the case of overlapped executions.

## Documentation
- Docs are updated in the API PR

## Is hotfix candidate?
- No
2024-11-04 20:48:23 +00:00
..