[FrankYang0529]

Why

• On Airflow 3.3+ and edge3 3.8.0+ run executor callbacks, such as the SyncCallback of a Deadline Alert, on Edge workers. With the default [edge] push_logs = True, the worker never reports whether the callback succeeded or failed.
• The worker pushes the callback's log with the job key that the Edge executor builds for callbacks. That key has dag_id="ExecuteCallback". The log route on the API server looks up a task instance for that key. No such task instance exists, so the route fails with HTTP 500. Even a callback whose code logs nothing leaves a non-empty log file, so the push fails for every callback.

How

• API server: for a callback job, the log route reads log_path from the workload JSON that the scheduler stored in the command column of the edge_job row. The worker reads the callback log from that same relative path. For a callback whose row or log_path is missing, both log routes return 404 instead of 500.
• Worker: pushing logs is now best effort. The worker logs an error from a push and still reports the final state. If pushes keep failing with 5xx, each push still waits for the client's retries, so the state can arrive a few minutes late. The worker change also handles an older API server that does not have the log route change above.

---

Was generative AI tooling used to co-author this PR?

• Yes - Claude Code