amoghrajesh commented on code in PR #73030: URL: https://github.com/apache/airflow/pull/73030#discussion_r4070466663
########## providers/common/ai/docs/retry_policies.rst: ########## @@ -140,10 +140,12 @@ four fields: ``category``, ``should_retry``, ``suggested_delay_seconds``, and ``reasoning``. Only ``should_retry`` and ``suggested_delay_seconds`` affect the run. -``category`` and ``reasoning`` are only recorded on a RETRY. They are written +``category`` and ``reasoning`` are recorded on both outcomes. They are written to the task instance's ``retry_reason`` (truncated to 500 characters, see -below), then cleared once the next attempt starts running. On a FAIL they are -not written anywhere -- they only show up in the task log. +below). On a RETRY the value is cleared once the next attempt starts running. +A FAIL is terminal, so there is no next attempt to clear it and the reason +stays on the row. When the model asked to retry but no attempts were left, the +stored reason ends with a ``; retries exhausted (N of M)`` note. Review Comment: All three fixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
