The Senate rejected Tim Kaine's war powers resolution on March 4, five days after US-Israeli strikes killed Ayatollah Ali Khamenei and launched Operation Epic Fury. The vote was 47-53 and broke almost entirely along party lines: every Democrat voted for it except John Fetterman, every Republican voted against it except Rand Paul. The resolution would have required Trump to remove US forces from hostilities against Iran unless Congress OK'd it. The resolution wouldn't have prevented the US from defending itself or Israel from Iranian attack.

A lot of the debate centered around a 1973 War Powers Act, which requires the President to notify Congress within 48 hours of deploying armed forces into hostile situations and says that forces be withdrawn within 60 to 90 days -- unless Congress says otherwise.

1. He Has the Authority and You Know It (Senate Majority Leader John Thune, Sen. Kevin Cramer)

The president is the commander-in-chief. He's not exceeding his powers. He's doing exactly what previous presidents did -- and you didn't complain then.

This is simple, people. Senate Majority Leader John Thune put it bluntly: "I think the president has the authority that he needs to conduct the activities, the operations that are currently underway there." He disputed that the War Powers Act requires an Authorization for Use of Military Force beyond 60 days, saying Trump's actions are "consistent with what previous administrations have done."

It's constitutional bedrock. Senator Kevin Cramer said the Constitution gives the president a lot of latitude and power in this sort of conflict. "And in my mind, he certainly hasn't exceeded that or even close as of now." Gene Hamilton, former White House deputy counsel and president of America First Legal, backed this up: the president has "broad inherent authority under Article II of the Constitution to defend U.S. interests and safety."

House Speaker Mike Johnson went further. He called the resolution "a terrible, dangerous idea" -- it would empower our enemies and weaken the country. He also argued that "we're not at war right now" -- instead, the operation was a limited, targeted combat.

2. Of Course This Is War, and Congress Didn't Approve It (Sen. Tim Kaine, Sen. Chuck Schumer, Ilya Somin)

The Constitution says Congress declares war. The president killed a foreign leader and launched a military campaign. If that's not war, nothing is.

Chuck Schumer framed the vote as a moral line. On the Senate floor, he said: "Do you stand with the American people who are exhausted with forever wars in the Middle East or stand with Donald Trump and Pete Hegseth as they bumble us headfirst into another war?"

The constitutional argument is straightforward. Under Article I, Section 8, Congress has the sole power to declare war. The president can respond to imminent threats under Article II, but launching a sustained military campaign against a sovereign nation -- killing its leader, destroying its navy, targeting its nuclear sites -- goes well beyond self-defense. The War Powers Act requires congressional authorization after 60 days. Kaine's resolution was designed to enforce that.

Many legal scholars aren't buying the White House's framing either. Ilya Somin, a law professor at George Mason University and scholar at the libertarian Cato Institute, was blunt: "This is very obviously a war." The framers at the Constitutional Convention in 1787 deliberately changed Congress's power from "make war" to "declare war" -- specifically to let presidents respond to sudden attacks, not to let them launch sustained campaigns.

3. Many Moderates Flinched (Sens. Collins, Murkowski, Young)

Even the Republicans who said they wanted oversight voted no -- because opposing the president during an active operation felt like a step too far.

The most revealing votes were the Republican moderates who agonized but fell in line. Susan Collins, Lisa Murkowski, and Todd Young had all previously voted for restrictions on military action in Venezuela. This time, they voted no.

Todd Young, who sits on the Senate Intelligence Committee, articulated the tension most clearly. He called for "congressional oversight and hearings" to keep Americans informed about the operation. But he voted against the resolution anyway, arguing: "Danger will only grow if we limit the president's military options at this critical moment." He called Iran "a core threat" to US national security.

Murkowski tried to split the difference with words. "I don't want today's vote to be interpreted that I don't think that Congress has a role," she said. But her vote said otherwise. The pattern across all three moderates was the same: express concern, call for oversight, then vote to let the president continue. The War Powers Act has been on the books for 53 years, and Congress has never successfully used it to stop a president from fighting.

Where This Lands

The vote changes nothing operationally -- Trump didn't need congressional approval to continue, and he wasn't going to get it anyway. What it does is extend a decades-long precedent: when a president commits forces, Congress talks about its authority and then declines to exercise it. The 60-day War Powers clock is ticking, but with the eighth resolution already dead, it's hard to imagine the ninth will be different. The real audience for the vote wasn't the military, it was the record. So every senator is on paper for what they did, or didn't do, while the United States was at war with Iran -- assuming this is "war" in the first place.

Sources