Why the Congress Failed to Check War Powers in Iran

Why the Congress Failed to Check War Powers in Iran

The US Constitution isn't a suggestion. It’s a blueprint. But this week, the US House of Representatives joined the Senate in a decision that basically hands the keys of the military to the executive branch without a second thought. By voting down a war powers resolution that would’ve forced President Trump to seek congressional approval for ongoing hostilities in Iran, lawmakers didn't just support a specific military campaign. They effectively abdicated their most solemn duty.

It’s a massive shift. For years, we’ve heard talk about "ending forever wars," yet when the opportunity arose to actually use the War Powers Resolution of 1973, the majority of the House chose to step aside. This wasn't a landslide; the 219-212 vote in the House followed a similarly narrow 47-53 defeat in the Senate. The results were largely split along party lines, proving that when it comes to the life-and-death stakes of war, tribalism still wins.

The Constitutional Loophole Nobody Wants to Close

The core of the argument against the resolution, championed by House Speaker Mike Johnson and Senate GOP leaders, is that reining in the President during active hostilities is "dangerous." They argue it "kneecaps" the commander-in-chief and sends a message of weakness to Tehran. But that’s a convenient excuse to ignore Article I, Section 8.

Congress has the sole power to declare war. The President is the commander-in-chief once that war starts. Somewhere in the last few decades, we’ve flipped that script. Now, the President starts the fight, and Congress is told it’s too "risky" to stop him. If we can't debate the merits of a war while it's happening, when can we?

  • The Senate Vote: Led by Tim Kaine and Rand Paul, the resolution failed on Wednesday. Only Paul crossed the aisle to support it, while Democrat John Fetterman broke ranks to vote with Republicans.
  • The House Vote: On Thursday, Representatives Thomas Massie and Ro Khanna’s version met a similar fate. Two Republicans (Massie and Warren Davidson) voted for it, while four Democrats voted against it.

What’s wild is that this conflict is already taking a toll. Six American servicemembers are dead. Over 1,000 people in Iran have been killed. We’re seeing oil tankers exploding near Kuwait and shipping insurance rates skyrocketing. Yet, the official line from the Pentagon—specifically Defense Secretary Pete Hegseth—is that the US is "just getting started."

Shifting Justifications and Mission Creep

One of the biggest frustrations for those of us watching this from the outside is the lack of a clear "why." First, we were told it was about an imminent threat. Then it was about dismantling a nuclear program. Now, it’s about "finishing the job." This is the definition of mission creep.

When you don't have a formal authorization for use of military force (AUMF), the goals can change every time a new press release drops. Without the resolution, there’s no requirement for the administration to define what "victory" looks like. We’ve seen this movie before in Iraq and Afghanistan. Honestly, it’s exhausting to watch the same mistakes happen with a different country’s name on the map.

What This Means for the 1973 War Powers Act

The War Powers Act was designed specifically for this moment. It was a reaction to the Vietnam War, meant to ensure that no president could drag the country into a long-term conflict on a whim. It mandates that any unauthorized engagement must be capped at 60 days, with a 30-day withdrawal window.

By voting these resolutions down, Congress is signaling that the 60-day clock doesn't really matter if the majority party supports the President. It makes the law a toothless tiger. If the President can ignore the requirement for authorization and Congress refuses to enforce it, the law only exists on paper.

The Immediate Fallout

The failure of these resolutions has immediate, real-world consequences:

  1. Unchecked Escalation: With no legislative hurdle, the administration can now consider ground troops or expanded naval strikes without fear of a budget freeze or legal block.
  2. Economic Instability: The Strait of Hormuz is a global chokepoint. With the conflict widening, expect gas prices and global food production (due to fertilizer shortages) to stay volatile.
  3. Political Precedent: This sets the stage for future presidents—of any party—to cite this moment as a reason why they don't need to ask for permission.

Your Next Steps

If you're concerned about how war powers are being handled, waiting for the next election isn't your only option. You can track how your specific representative voted on H.Con.Res. 38 or the Senate version. Use the Office of the Clerk or Senate.gov to see the roll call.

Don't just look at the party label. Look at the individual. If they talk about "constitutional originalism" but voted to give up their war-making power, call their office. If they ran on an anti-war platform but voted to continue unauthorized strikes, ask for a justification. The only way the War Powers Act regains its teeth is if the people who vote in the lawmakers actually demand they use it.

The 60-day deadline under the War Powers Act for the Iran conflict is approaching at the end of April. That’s the next major flashpoint. Watch that date. If no authorization is sought by then, we aren't just in a war; we're in a constitutional crisis.

LY

Lily Young

With a passion for uncovering the truth, Lily Young has spent years reporting on complex issues across business, technology, and global affairs.