pause/unpause dag logs wrong event status

[achharKalia]

Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

IN version 2.5.1 release, airflow pause/unpause dag button on dags page doesn't work properly.
When we pause a dag in the audit logs its show dag as unpaused.
and when we unpause any dag audit log shows a dag is paused. Also sometimes dag runs properly as per schedule and sometime doesn't because of this problem.

IN recent dag behaviour, we enabled the dag on friday and dag was scheduled to run on Monday but it didn't. It was a active dag not paused in blue color. However in the dag audit logs, it was showing below :

2023-06-12, 17:42:57	None	paused	None	achhar.kalia	[('is_paused', 'false'), ('dag_id', 'resdex-usage-mis-w')]
2023-06-08, 17:53:02	None	paused	None	pawan.shaw@naukri.com	[('is_paused', 'true'), ('dag_id', 'resdex-usage-mis-w')]

What you think should happen instead

when we pause, it should say its paused, when we unpause or resume, it should give message that dag is in unpause or resume state.

How to reproduce

try, for me this is still live problem in 2.5.1

Operating System

centos 7

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

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

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[achharKalia]

hi, ANy update on the issue,

[utkarsharma2]

Since you checked in Are you willing to submit PR? section, I assumed you wanted to open a PR for the issue :)

[achharKalia]

yes, I want to open PR.

[potiuk]

Assigned you then :)

[achharKalia]

any luck you are able to find.

[gustavohwulee]

not sure if this is related but in this version 2.5.1 when we try to pause a dag programatically the value is not logged to the audit logs if it runs by the scheduler.