New RunLLM response generated: >>>*# Question* When I upgraded

flytekit

to

1.13.7

while the backend

flyte

version was

1.13.1

, I got the following system error running remote workflow

RuntimeExecutionError: max number of system retry attempts [51/50] exhausted. Last known status message: worker error(s) encountered: [0]: failed at Node[n0]. RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [sidecar]: [BadTaskSpecification] invalid TaskSpecification, primary container [primary] not defined

Could it be caused by

flytekit

version being ahead of

flyte

version? How does version compatibility work? # Answer Yes, the error could be caused by the

flytekit

version being ahead of the

flyte

backend version. Flyte's components are designed to be backward compatible, but there can be issues when the SDK (

flytekit

) is ahead of the backend components. According to this discussion, the backend should support older versions of

flytekit

, but there is no comprehensive compatibility grid available. Would you like more detailed steps or further assistance? Sources: - this discussion Slack Link https://.slack.com/archives/CP2HDHKE1/p1728062610.180589 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.