flyteorg/flyte

[Run Service] Ensure `ListActions` works expected

Closed

#6,980 opened on Mar 6, 2026

View on GitHubContributor guide
 (2 comments) (0 reactions) (1 assignee)Python (378 forks)batch import
flyte2good first issue

Repository metrics

Stars
 (3,705 stars)
PR merge metrics
 (Avg merge 3d 8h) (114 merged PRs in 30d)

Description

Command

RUN_NAME=run-1772757248 LIMIT=20 bash runs/test/scripts/list_actions.sh

Response

Field Expected Presented? Need implement?
actions repeated Action ✅ ❌
token string ✅ ❌
actions[].id ActionIdentifier ✅ ❌
actions[].id.run.org string ✅ ❌
actions[].id.run.project string ✅ ❌
actions[].id.run.domain string ✅ ❌
actions[].id.run.name string ❌ ✅
actions[].id.name string ✅ ❌
actions[].metadata ActionMetadata ✅ ❌
actions[].metadata.parent string ✅ ❌
actions[].status ActionStatus ✅ ❌
actions[].status.phase ActionPhase ✅ ❌
actions[].status.start_time Timestamp ❌ ✅
actions[].status.end_time optional Timestamp ❌ ✅ (available when the action terminated)
actions[].status.attempts uint32 ❌ ✅
actions[].status.cache_status CatalogCacheStatus ❌ ✅
actions[].status.duration_ms optional uint64 ❌ ✅ (available when the action terminated)

Contributor guide

Research direction
Examine the `runs/test/scripts/list actions.sh` script and the corresponding service implementation. The missing fields (`id.run.name`, `status.start time`, `status.end time`, `status.attempts`, `status.cache status`, `status.duration ms`) need to be added to the ListActions response. Check the proto definitions for `Action` and `ActionStatus`, and the service code that constructs the response. The issue has an assignee, so coordinate before implementing.
Tech stack
pythongrpc
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GogRPCprotobufFlyte codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30