Yes, you can access the execution domain within a Flyte workflow or task using the Python SDK. In a Python task, use

flytekit.current_context().execution_id.domain

to retrieve the domain of the current execution. This is supported for Python tasks running on Kubernetes, but may not be available in all plugin types (e.g., Databricks tasks) or in all execution environments. There is no documented way to access the execution domain directly from a workflow definition itself—access is via the task context only. If you need to access the domain in other plugin types or environments, you may need to pass it explicitly as a workflow input, as this is a known limitation and an open feature request for some plugins. Would you like more detail or code examples for accessing the execution domain in tasks? Sources: - Flyte core issue: Make execution_id and execution_domain available for plugins 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.