Strikes on Iran Resume and Restart the War Powers Clock in Congress

What happened this week

On July 10, 2026, President Trump formally notified Congress that the United States had resumed military strikes against Iran, action he said began on July 7 (Roll Call, July 13, 2026; The Hill, July 13, 2026). The administration described the strikes as a response to Iranian attacks on commercial vessels in the Strait of Hormuz, the shipping lane that carries a large share of the world's seaborne oil (Roll Call, July 13, 2026). U.S. Central Command said its forces hit targets inside Iran, and Congress returned to Washington this week to a Senate roster still absorbing the death of Sen. Lindsey Graham and a legislative calendar that now includes a fresh question about a war (NPR, July 13, 2026).

The notice matters beyond the headlines because of what it starts. The conflict that began in February 2026 had wound down enough by the spring that the administration told Congress hostilities had terminated, an argument that, if accepted, stops the legal timeline the War Powers Resolution sets running (Roll Call, July 13, 2026). The resumption of strikes reopened that timeline, and it did so in front of a Congress that had already gone on record against the fight.

The clock the notice restarts

The War Powers Resolution of 1973 is a reporting-and-clock statute, not a ban on the use of force. It requires the president to notify Congress within 48 hours of introducing armed forces into hostilities, and it then gives Congress a window of 60 days, extendable by 30 more, after which forces are to be withdrawn absent a declaration of war or specific authorization (Al Jazeera, June 28, 2026; Congress.gov, Understanding the War Powers Resolution, 2024). Trump's July 10 letter is the notification that starts the count. On its face, the window runs into early September before the law's deadline arrives.

The clock has a weak enforcement history. Presidents of both parties have argued that the 60 day rule is either advisory or unconstitutional, and courts have generally declined to referee the dispute between the two political branches (Congress.gov, Understanding the War Powers Resolution, 2024). What the statute reliably produces is a paper trail and a privileged vehicle: it lets any member force a floor vote on withdrawal that leadership cannot easily bury. That is the tool Congress reached for in June, and it is the one available again now.

What Congress already said in June

Before the strikes resumed, both chambers had already voted to end the involvement. On June 3, 2026, the House passed a concurrent war powers resolution directing the president to remove U.S. forces from hostilities with Iran, 215 to 208, with four Republicans joining Democrats: Reps. Tom Barrett of Michigan, Warren Davidson of Ohio, Brian Fitzpatrick of Pennsylvania, and Thomas Massie of Kentucky (CNN, June 3, 2026; NPR, June 3, 2026). On June 23, the Senate passed the same measure 50 to 48, with four Republicans crossing over: Sens. Bill Cassidy of Louisiana, Susan Collins of Maine, Rand Paul of Kentucky, and Lisa Murkowski of Alaska (NPR, June 23, 2026; CNN, June 23, 2026).

It was the first time both chambers passed a war powers resolution directing a president to pull forces out of an active conflict (ASIL, June 2026). It also carried no force of law. A concurrent resolution is not presented to the president for signature, so the June votes were a formal statement of the congressional position, not a binding order (ASIL, June 2026; NPR, June 23, 2026). The gap between what Congress said and what it can compel is the whole story of the War Powers Resolution, and the July notice puts that gap back on the floor.

How often this notice gets filed

Presidents file these reports more often than most readers assume, and the numbers put this week's letter in context. Since 1973, presidents have submitted more than 130 reports to Congress under the War Powers Resolution (Wikipedia, War Powers Resolution, 2026). The load is concentrated in a few administrations: President Clinton filed 60, President George W. Bush 39, President Reagan 14, President Obama 11, President George H. W. Bush 7, President Ford 4, and President Carter 1 (Wikipedia, War Powers Resolution, 2026). Deployments to Lebanon, the 1991 Persian Gulf War, the Balkans, and a long list of smaller operations all generated one.

Against more than 130 notifications across five decades, the count of times Congress used the statute to actually force a president to stop is effectively zero. That asymmetry is why the June votes drew attention as a first, and why the July notice is more a political and constitutional marker than a countdown anyone expects to expire on schedule. US Political Rank scores commanders in chief on documented results rather than rhetoric in its ranking of presidents by foreign policy outcomes, where the use of force and its consequences are weighed against stated goals.

What to watch

Three markers will tell the story from here. First, whether any member forces a privileged floor vote on a binding joint resolution, the version that would be presented to the president, rather than the concurrent measure that passed in June. Second, the arithmetic: Republicans hold 53 Senate seats to 47 for the Democratic caucus once South Carolina's interim appointee is seated, so a binding withdrawal measure would need defections well beyond the four Republicans who crossed over in June (Wikipedia, List of current United States senators, 2026). Third, the calendar. The 60 day window opened by the July 10 notice runs into early September, and the practical question is not whether the deadline forces a withdrawal, because history says it will not, but whether the vote it enables changes the political price of the operation. Congress said its piece in June. The clock is running again, and this time the strikes are ongoing.