What do you see as an issue?

Template fields documentation does not include much detail about asset-triggered DAGs and is mostly focused on classical "time-based" DAGs.

For example, it does not mention that asset-triggered DAGs don't have loglical_date, ds, etc in Airflow 3.
Another example, the description of task_instance_key_str is A unique, human-readable key to the task instance. The format is ``{dag_id}__{task_id}__{ds_nodash}``. which is not correct for asset-based worfklows:

Might be a good first issue. I could submit a pull request as well but not this/next week, so would be happy if someone would like to give it a shot.

Solving the problem

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct