suii2210 commented on issue #59795: URL: https://github.com/apache/airflow/issues/59795#issuecomment-3691711238
Thanks for the detailed report -this does look like a genuine schema-level bug. The `external_executor_id` column is currently limited to VARCHAR(250) in `task_instance` and `task_instance_history`, but executors like the AWS Lambda Executor can legitimately generate longer, structured identifiers (dag_id, task_id, run_id, map_index, etc.). Since `external_executor_id` is opaque metadata from Airflow’s perspective, enforcing such a small fixed length can cause scheduler crashes, as seen here. This issue is also not AWS-specific and could affect any external executor that manages tasks outside Airflow. A more robust fix would be to increase the column type (e.g. to TEXT) for both tables, along with a migration, rather than relying on executors to truncate IDs. Happy to contribute in this . -- 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]
