[Run Service] Ensure `ListRuns` works expected

[machichima]

Need to fix ListRuns to work correctly

Response

Field	Expected	Presented?	Need implement?
runs	repeated Run	✅	❌
token	string	❌	✅ (need to ensure we get token when we set limit and there’s next page)
runs[].action	Action	✅	❌
runs[].action.id	ActionIdentifier	✅	❌
runs[].action.metadata	ActionMetadata	✅	❌
runs[].action.status	ActionStatus	✅	❌
runs[].action.status.phase	ActionPhase	✅	❌
runs[].action.status.start_time	Timestamp	❌	✅
runs[].action.status.end_time	optional Timestamp	❌	✅ (need to ensure this presented for the terminated run)
runs[].action.status.attempts	uint32	❌	✅
runs[].action.status.cache_status	CatalogCacheStatus	❌	✅
runs[].action.status.duration_ms	optional uint64	❌	✅ (need to ensure this presented for the terminated run)

[runllm]

It seems likely that the ListRuns method in Flyte's Run Service should return a paginated list of runs, including a token for pagination, and each run should have detailed action status fields such as start_time, end_time, attempts, cache_status, and duration_ms. The data sources confirm that runs and runs[].action fields are present, but do not explicitly confirm that token and all detailed status fields are always included in the response, especially for pagination and terminated runs.

Based on the Flyte SDK Run API reference and the SDK implementation, it appears that the token for pagination and some detailed status fields (like start_time, end_time, attempts, cache_status, duration_ms) may need to be explicitly implemented or ensured in the response, particularly for correct pagination and for terminated runs. Would you like a step-by-step breakdown of how to address these missing fields?

Sources:

• Flyte SDK src/flyte/remote/_run.py
• Flyte SDK Run API reference

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[0yukali0]

#take