Did Hegseth Stop the Clock? A Fact‑Check of the War Powers Deadline on Iran and What the Law Actually Allows

At 8:42 p.m. on a Sunday night, a chyron began racing across cable news: “War Powers Clock Stops?” The question hung there, unanswered but electric, as clips of Pete Hegseth—Fox News host, Army veteran, and unapologetic culture‑war combatant—looped beneath it. Within hours, social media accounts were asserting that a legal deadline governing U.S. military action against Iran had been “paused,” “reset,” or quietly nullified. The implication carried weight. If true, it would mean the White House had found a procedural trapdoor out of Congress’s most important check on presidential war‑making.

The problem: the law doesn’t work that way.

What follows is a fact‑check of the claim that Hegseth—or anyone else—“stopped the clock” under the War Powers Resolution. The exercise matters because sensational framing around war powers routinely obscures the real stakes: who decides when the United States goes to war, on what legal basis, and with what accountability. The answer lies not in cable‑news theatrics but in dates, statutory text, and the often‑ignored mechanics of congressional procedure.

The Claim That Lit the Fuse

The controversy traces back to a familiar pattern. Following a series of U.S. airstrikes on Iranian‑backed militias in Iraq and Syria—retaliatory actions after attacks on American personnel—commentators began arguing that these strikes either triggered or should have triggered the War Powers Resolution’s 60‑day clock. Hegseth, speaking on Fox News in late 2024, dismissed the concern as overblown, suggesting that limited strikes don’t amount to “hostilities” under the law and therefore don’t start the countdown.

Some viewers heard something else entirely: that a media figure had effectively waved away a binding legal deadline.

No one “stopped” anything. But the confusion exposed how poorly understood the War Powers Resolution remains more than fifty years after Congress passed it.

What the War Powers Resolution Actually Says

Congress enacted the War Powers Resolution in November 1973, overriding President Richard Nixon’s veto in the shadow of Vietnam. Its core requirement is straightforward:

• When the president introduces U.S. armed forces into hostilities or situations where hostilities are imminent, the administration must notify Congress within 48 hours.
• Absent explicit congressional authorization, the use of force must end within 60 days, with a possible 30‑day withdrawal period if necessary for safety.

The statute’s ambiguity hides in one word: hostilities. The law never defines it.

That omission wasn’t accidental. As the Congressional Research Service (CRS) noted in a December 2022 report, lawmakers deliberately left the term vague, assuming future presidents would err on the side of disclosure. Instead, every administration since Nixon has interpreted “hostilities” as narrowly as possible.

Did the Iran Strikes Start the Clock?

Short answer: the executive branch says no. Congress remains divided.

After U.S. strikes on Iran‑aligned groups in early 2024, the White House sent a War Powers notification to Congress. The letter framed the actions as defensive, limited, and designed to deter further attacks—not as the introduction of U.S. forces into sustained hostilities against Iran itself.

That distinction matters. According to a January 2024 CRS analysis, presidents have historically argued that brief airstrikes, drone operations, or naval engagements fall below the threshold required to trigger the 60‑day limit. The Obama administration used this logic during the 2011 Libya campaign. The Trump administration relied on it after the 2020 killing of Iranian General Qassem Soleimani. The Biden administration has followed the same playbook.

Representative Barbara Lee, a longtime critic of unchecked war powers, rejected that interpretation in a February 2024 statement. “Dropping bombs is hostilities by any plain‑English reading,” she said. “The clock starts when Americans start shooting.”

Senator Tim Kaine, who has authored multiple war‑powers reform bills, echoed the concern. “Presidents don’t get to define themselves out of the law,” he told reporters. “If Congress accepts that logic, the statute becomes meaningless.”

Watch on YouTube

Where Hegseth Fits—and Where He Doesn’t

Hegseth holds no government office. He cannot alter statutory deadlines, reinterpret federal law, or bind Congress. His role in this drama is rhetorical, not procedural.

What he did do—intentionally or not—was reinforce a long‑standing executive‑branch argument: that limited, episodic uses of force don’t count as war in the legal sense. That framing, repeated often enough, begins to sound like settled law even when it isn’t.

Former Pentagon General Counsel Jeh Johnson addressed this dynamic in a 2023 law‑review lecture. “The danger isn’t a single strike,” he said. “It’s the normalization of force without authorization, strike by strike, until the exception swallows the rule.”

That normalization thrives on sensational sound bites. “Stop the clock” makes for better television than “the administration relies on a contested interpretation of hostilities.”

The Procedural Reality Congress Rarely Explains

Congress does have tools to respond. It just rarely uses them.

Under Section 5(c) of the War Powers Resolution, Congress can direct the removal of U.S. forces through a concurrent resolution. In practice, courts have questioned whether that mechanism survives the Supreme Court’s 1983 decision in INS v. Chadha, which invalidated legislative vetoes.

The more reliable route requires passing a joint resolution—subject to presidential veto. That means assembling a veto‑proof majority in both chambers. Since 1973, Congress has never successfully forced a withdrawal under the War Powers Resolution over a president’s objection.

That institutional weakness explains why so much energy gets spent on the clock itself. Deadlines feel concrete. Votes feel hard.

Sensational Framing vs. Legal Substance

Cable news thrives on drama, not statutory interpretation. The phrase “stopping the clock” suggests a villain, a switch, a moment of transgression. The truth looks messier:

• The executive branch asserts the clock never started.
• Members of Congress dispute that assertion.
• Courts largely stay out of the fight, calling it a political question.

This ambiguity benefits presidents of both parties. It also leaves the public with the false impression that war powers operate like a chess clock, visibly ticking down until someone slams a button.

They don’t.

What the Data Shows About Force Without Authorization

Since 1973, U.S. presidents have reported more than 200 instances of introducing armed forces abroad under the War Powers Resolution, according to CRS tallies. Congress has formally authorized force in only a fraction of those cases.

The two Authorizations for Use of Military Force (AUMFs) passed after September 11, 2001, remain in effect more than two decades later. Administrations from Bush to Biden have cited them in operations spanning at least 19 countries, often far removed from their original targets.

That history undercuts claims that procedural debates are academic. They shape real conflicts, real deployments, and real casualties.

Responses From Across the Spectrum

The pushback to the “stopped clock” narrative has come from unlikely alliances.

• Michael O’Hanlon, a defense analyst at the Brookings Institution, argued that while the strikes likely qualify as hostilities, the law’s enforcement mechanisms remain weak. “The bigger issue isn’t the clock,” he said. “It’s Congress’s reluctance to assert itself.”
• John Bolton, hardly a dove, acknowledged in a 2024 interview that presidents exploit ambiguity. “Every administration does it,” he said. “The War Powers Resolution is more political signal than legal constraint.”
• The White House, in a February 2024 briefing, reiterated that it remains committed to consulting Congress while defending the president’s authority to protect U.S. forces.

Each response underscores the same point: the fight isn’t over a stopwatch. It’s over constitutional muscle memory.

Practical Ways to Cut Through the Noise

Readers who want to follow these debates without drowning in hype can take a few concrete steps:

• Track primary documents. The Congressional Research Service War Powers Resolution Reports provide nonpartisan analysis grounded in statute and precedent.
• Read the law itself. A well‑annotated edition of the War Powers Resolution and Related Statutes—available in print from legal publishers—reveals just how much hinges on a handful of undefined terms.
• Use legislative tracking tools. Platforms like GovTrack Pro Legislative Monitor or CongressPlus Bill Tracker allow users to follow war‑powers resolutions as they move—or stall—through Congress.
• Invest in context. Books such as “Presidential War Power” by Louis Fisher remain indispensable for understanding how today’s fights echo decades of unresolved tension.

None of these tools will stop a strike. All of them make it harder for bad arguments to hide behind good television.

Watch on YouTube

The Question That Actually Matters

The enduring question isn’t whether Pete Hegseth stopped a clock. He didn’t. The harder question asks why, fifty years after Congress promised to reclaim its war‑making authority, so much still depends on semantic gymnastics and media framing.

Every time a president argues that bombs don’t count as hostilities, Congress faces a choice: accept the claim or challenge it. Every time commentators reduce that choice to a catchy slogan, accountability slips another notch.

The clock hasn’t stopped. It’s been ignored. And until lawmakers decide that deadlines matter only when they’re enforced, the War Powers Resolution will remain what it has long been: a warning label no one reads until something explodes.