Senate Blocks Attempt to End Trump’s Iran War Again — For the 13th Time

The Senate voted 49-50 on Thursday, July 30, 2026, against advancing a war powers resolution offered by Sen. Kirsten Gillibrand, D-N.Y., that would have required President Trump to withdraw U.S. forces from combat operations against Iran absent specific congressional authorization. It was the 13th time the chamber has voted on a resolution to end the Iran war since fighting began in February 2026, and only one nonbinding measure has ever passed. Republicans Rand Paul of Kentucky, Susan Collins of Maine and Lisa Murkowski of Alaska crossed over to vote with 49 Democrats in favor of advancing the resolution, while Democrat John Fetterman of Pennsylvania voted with the majority to block it [1].

The vote came a day after the U.S. military carried out a fresh wave of strikes on Iran, following Iranian ballistic missile launches that were intercepted earlier in the week. The war has now killed 18 American servicemembers and wounded more than 600, according to Senate figures cited during debate. Gillibrand argued on the floor that “under the Constitution, we have the power to end this war today. Let’s use it,” pointing to casualties, fuel costs and a lack of administration accountability [2].

Why It Sucks:

Trump Administration & Republican Hawks

• Democrats keep forcing symbolic votes. Republicans note this is the 13th such resolution since February, arguing Democrats are using the Senate floor to score political points rather than legislate while active combat operations are underway [1].
• Mid-war handcuffs endanger troops. GOP hawks contend that tying the commander-in-chief’s hands mid-conflict, after Iran just launched ballistic missiles at U.S. forces, signals weakness to Tehran and puts deployed servicemembers at greater risk [2].
• Cassidy’s flip shows the politics, not principle. Sen. Bill Cassidy voted against advancing the measure after previously supporting similar resolutions, underscoring GOP leadership’s view that this is a messaging exercise rather than a genuine constitutional dispute [1].

Progressive & Antiwar Democrats

• Eighteen dead and Congress won’t act. Gillibrand and allies point to 18 killed and over 600 wounded servicemembers as proof the war has real human costs that Congress has a constitutional duty to check [2].
• Fetterman’s defection stings. Progressives are furious that a Democrat, John Fetterman, supplied a vote to block the resolution, arguing it undercuts the party’s ability to present a unified front against an unauthorized war [1].
• No off-ramp in sight. With a ceasefire having already failed and Iran retaliating with missiles this week, antiwar Democrats warn the conflict is escalating with no congressional vote ever having authorized it [2].

War Powers Constitutionalists

• Article I is being ignored regardless of party. Rand Paul, Susan Collins and Lisa Murkowski crossed party lines specifically because they see this as a separation-of-powers issue, not a referendum on Iran policy itself [1].
• A one-vote margin shows how close it was. The 49-50 tally means a single senator flipping would have forced the administration to seek formal authorization, a reminder that Congress has repeatedly declined to reclaim its own war-declaring power by the thinnest of margins [1].
• Repeated votes without teeth erode the Constitution. Constitutionalists argue that when war powers resolutions fail 13 times in a row without consequence, the precedent normalizes unilateral executive war-making for future presidents of either party [2].

Sources & Citations:

[1] Roll Call: Iran war powers resolution blocked in Senate as conflict heats up
[2] The Hill: Senate Republicans defeat Iran war powers resolution