The War Powers Resolution clock started on February 28, 2026, the day US forces participated in strikes on Iran. Under the 1973 law, the president must notify Congress within 48 hours of introducing forces into hostilities. After 60 days without congressional authorization, the president must withdraw.
April 28 is the deadline. You will read many pieces describing it as a constitutional hard stop. You will read fewer pieces noting that this mechanism has never stopped a war.
Not once. Not in 53 years of the War Powers Resolution's existence.
Presidents have notified Congress under the War Powers Resolution dozens of times since 1973. In every significant case — Lebanon (1982), Grenada (1983), Panama (1989), Iraq (1991), Somalia (1993), Haiti (1994), Bosnia (1995), Kosovo (1999), Afghanistan (2001), Iraq (2003), Libya (2011), Syria (2017, 2018), Iran strikes (2020) — Congress either authorized the action, passed a resolution too weak to force withdrawal, or did nothing and let the deadline pass.
The one partial exception: the 1973 cutoff of funds for combat operations in Cambodia and Laos, which was a specific appropriations restriction, not an invocation of the War Powers mechanism itself. And it required a veto override that came only after the war was already functionally ending.
Libya 2011 is instructive. The 60-day clock expired. The House passed a resolution declaring the administration had not met the requirements of the law. Obama continued operations. Nothing happened. The mechanism had no enforcement teeth, and Congress had no appetite to use the only teeth it had — appropriations.
The structural problem is simple: voting to end a war is politically catastrophic in ways that voting to authorize one is not. If you vote to withdraw and something goes wrong — a hostage killed, an ally abandoned, an adversary emboldened — you own it. If you vote to continue and something goes wrong, you share it with the executive.
The asymmetry is total. The upside of forcing withdrawal is procedural vindication of a 53-year-old statute. The downside is a generation of attack ads showing you voting to retreat from a war with Iran while US forces were in the field.
There is also the factional problem. Any resolution to invoke War Powers needs majority support. The Republican caucus will not provide it. Democratic hawks will not provide it. The antiwar faction exists but it is not a majority and it knows that forcing a withdrawal vote they might lose is worse than not forcing one.
So the clock ticks. April 28 arrives. A few speeches are given about constitutional prerogative. The operations continue.
The War Powers Resolution was passed in 1973 over Nixon's veto as a reaction to Vietnam — a war that expanded for years through executive action with no formal congressional declaration. The theory was: require notification, set a deadline, force a vote.
The error in the theory was assuming Congress wanted to vote. It didn't. It doesn't. Congress passes the buck on war for the same reason it passes the buck on deficits, drug pricing, and immigration: the vote is politically costly and the alternative — letting the executive act and maintaining deniability — is not. The law created a fire alarm. Congress doesn't pull fire alarms when the building is on fire with the public watching.
This is not a critique of any particular Congress. It is a structural observation about what legislative bodies do when given the option of accountability or avoidance. They choose avoidance. The War Powers Resolution assumed legislators would choose accountability. Fifty-three years of evidence says they won't.
If not the April 28 deadline, what stops this? What are the actual constraints?
The first is military: what can be achieved and at what cost. The nuclear infrastructure is destroyed (combined June 2025 and February 2026 strikes). The question is what comes next — regime decapitation, sustained degradation, or negotiated settlement with whoever emerges from the succession vacuum. Military planners have objectives; those objectives have completion conditions. When they're met or judged unattainable, operations scale down.
The second is economic: Brent oil. Kharg Island is at near-zero capacity. If Hormuz closes, the Gulf States are directly hit — Saudi Aramco exports, UAE LNG, Kuwaiti crude. A sustained Hormuz closure is a global recession trigger. This creates a real constraint: the operations cannot produce the kind of Iranian retaliation that closes the strait for more than a few days, because the economic blowback hits allied economies as hard as adversary ones. The oil market is the binding constraint, not the calendar.
The third is political: Trump's approval numbers and the 2026 midterm calendar. A short, decisive operation that "destroyed Iran's nuclear program" polls well. A grinding, escalating regional war that sends Brent to $120 and disrupts supply chains polls poorly. The political clock is not April 28 — it's the October 2026 midterm filing deadlines, when incumbents start calculating whether this war is an asset or a liability.
The useful questions are not about April 28. They are about:
Whether the IRGC accepts a successor or fractures — which determines whether there's anyone to negotiate a ceasefire with, or whether the war continues into a stateless target set.
Whether Hormuz traffic recovers — the tanker transit count over the next two weeks is a more reliable indicator of Iranian escalation intent than any statement from either side.
Whether Saudi Arabia stays neutral or tilts — a Saudi tilt toward the US-Israel axis provides the regional legitimacy for a negotiated outcome. Saudi neutrality or tilt toward Iran prolongs the conflict indefinitely.
Whether Brent holds below $90 — above $90 on a sustained basis, the economic pressure on allied governments becomes politically untenable and the coalition starts to fray.
These are the actual clocks. April 28 is theater. The mechanism rings every 60 days and nobody answers.
There is something revealing about the gap between the formal constraint and the effective one. The War Powers Resolution exists. It is law. It was passed with the explicit purpose of limiting presidential war power. And it has never, in 53 years, actually limited presidential war power in any significant way.
This is how a lot of institutional machinery works: the mechanism is real, the enforcement is not. The constraint only functions if the party with enforcement power chooses to use it, and the party with enforcement power consistently calculates that using it costs more than not using it.
What the War Powers Resolution actually does is create a reporting requirement and a political ventilation mechanism. Presidents file the notifications. Opposition members give speeches. Committees hold hearings. Op-eds are written about constitutional prerogative. And then the operations continue until the military or economic or political calculus changes — which happens on its own timeline, not April 28.
For forecasting purposes: the probability that War Powers invocation materially changes the Iran campaign is low. Under 5%. The question is what the actual constraints produce. Watch Brent, watch Hormuz transit data, watch the succession signals from Tehran. Those will tell you more about when this ends than the calendar on the wall that says April 28.