War Powers Resolution

On 23 July the House passed H.Con.Res.89 214-208, directing Trump to withdraw forces under the statute's own machinery; hours later the Senate's parallel measure, the binding S.J.Res.180, went down 47-49 on the same Roll Call, with only Susan Collins crossing over against four House Republicans. It is at least the seventh vote since March the statute has failed to convert into a binding order.

Three days later, on 26 July, the Pentagon retired the Operation Epic Fury label and folded Iran casualty reporting into a broader Overseas Operations category. For the statute, that renaming carries more weight than its wording lets on: if Epic Fury counts as having ended in May, the switch could start a fresh 60-day withdrawal clock, the exact trigger the Senate had just refused to pull by vote, so the resolution's teeth now hinge on an administrative filing rather than the vote Congress just held.

On 2 August Trump scrapped a planned strike on Iran, not because of anything the War Powers Resolution requires but because Saudi Crown Prince Mohammed bin Salman warned Gulf States would absorb the retaliation, a request Qatar and the UAE joined. Every previous halt in the fighting had come from inside the machinery this statute or its allies built: a munitions warning from General Dan Caine, the Senate's own failed vote on this resolution.

This pause came from outside Washington entirely. For a statute built on the premise that Congress, not a foreign head of state, checks a president's war-making, a stop ordered by Gulf diplomacy rather than a floor vote is a demonstration of exactly the gap the resolution has never closed.