[Run Service] Ensure `WatchRuns` works expected

[machichima]

Command

SCOPE=project bash runs/test/scripts/watch_runs.sh

Response

Field	Expected	Presented?	Need implement?
runs	repeated Run	✅	❌
runs[].action	Action	✅	❌
runs[].action.id	ActionIdentifier	✅	❌
runs[].action.id.run.org	string	✅	❌
runs[].action.id.run.project	string	✅	❌
runs[].action.id.run.domain	string	✅	❌
runs[].action.id.run.name	string	✅	❌
runs[].action.id.name	string	✅	❌
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	❌	✅ (available when the action terminated)
runs[].action.status.attempts	uint32	❌	✅
runs[].action.status.cache_status	CatalogCacheStatus	❌	✅
runs[].action.status.duration_ms	optional uint64	❌	✅ (available when the action terminated)

[runllm]

My understanding is that the WatchRuns API is referenced in the Flyte SDK's protocol definitions, and it returns a stream of run updates, each including a list of Run objects with nested Action details. The fields you listed (such as runs[].action.id.run.org, runs[].action.status.phase, etc.) are present in the protocol, but fields like start_time, end_time, attempts, cache_status, and duration_ms are not explicitly confirmed as implemented in the returned data—they are marked as needing implementation in your table. This suggests that while the structure supports these fields, their population in the response may not be complete yet and would require further implementation to match expectations.

For more detail on the protocol and available fields, see the relevant protocol definitions in the Flyte SDK source code, specifically the WatchRuns method and the Run, Action, and ActionStatus message structures. It seems likely that the missing fields are recognized as gaps and are planned for future implementation, but are not currently available in the response payloads as per your table and the available data sources (Flyte SDK protocols).

Would you like a step-by-step breakdown of the protocol structure or guidance on how to extend the implementation for the missing fields?

Sources:

• Flyte SDK protocols

---

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!

[muskan-creates352]

hi, I would like to work on this issue. Could you please assign it to me?

[mvanhorn]

Implemented in #7053 - populates StartTime, EndTime, Attempts, and DurationMs in all four conversion functions. CacheStatus is deferred since the Action model doesn't expose it as a direct field.

[muskan-creates352]

Thanks for the update! I noticed that CacheStatus is still not implemented. I would like to work on adding it. Could you please assign this part to me?

[machichima]

Hi @muskan-creates352 ,
Our colleague is working on adding CacheStatus to model. I'll let you know if it's still needed after his PR merged
Thanks!