Your migraine app wants an end time your migraine never gave you.
Most trackers seal the record when the pain stops. The fog, light sensitivity and fatigue that follow get thrown out, and so does the real length of the attack.
The prompt that asks for an end time you don't have
Nine hours after the triptan, the headache is gone and the app wants an answer. There's a field labeled 'attack ended' under the timeline, and the entry won't save until you fill it.
But you can't see the ending. The throbbing faded sometime in the early afternoon. Light from the kitchen window still stings, your neck feels bolted at the base of the skull, and you've read the same email three times without taking in a word. Is that still the attack? Is it over?
Plenty of people ask exactly that. A MigraineMeanderings post asked it in so many words: how do you determine when a migraine attack is over? On r/migraine, a thread about apps 'not made by someone who has migraines' hit the same nerve. The form assumes an answer your body never gives. So you type a guess, and the guess becomes your data.
The forced endpoint, named
Call it the forced endpoint: a required end time that closes the episode record the moment pain resolves.
It looks like a small interface choice. It's actually a data-model decision, and it carries a whole theory of migraine with it. That theory says an attack is discrete. Pain starts it, pain ends it, and everything worth knowing fits between two timestamps. Once you tap 'end', the record seals. Whatever you feel after that either goes unlogged or gets filed as a loose symptom with no link to the attack that caused it.
That theory doesn't hold for a large share of people with migraine, and it holds least for chronic migraineurs. The headache is one phase of a longer event. Premonitory symptoms can start hours before the pain. Postdrome can drag on for a day or more after it. A model with room for only the middle phase throws away both edges, and the back edge is usually the one that costs you the next day.
Why 'when the pain stops' feels like the right answer
Pain makes a tidy clock, and the field inherited it honestly.
Acute-treatment research has long scored success on pain freedom at two hours The IHS fourth edition (2019) guidelines for controlled trials of acute migraine treatment in adults specify the percentage of participants pain-free at 2 hours as the primary efficacy endpoint. ([source](https://www.neurologyadvisor.com/news/updated-guidelines-for-controlled-trials-of-acute-treatment-of-migraine/)). Clinic visits ask about headache days. Insurers count monthly migraine days when deciding who qualifies for preventive treatment. Every one of those systems runs on pain, so building a tracker around pain onset and pain offset looks like plain common sense.
Pain freedom at two hours answers one narrow question, though: did the drug knock the headache down? Trackers borrowed that clock and pointed it at the whole attack. And pain is the easiest symptom to timestamp, because it has a felt edge. Fog doesn't. Fatigue doesn't. Residual photophobia fades rather than switching off. A field that only accepts a sharp edge will always favor the symptom that has one.
What the research says about the hours after the headache
The classification itself measures the headache phase. ICHD-3 sets a duration of 4 to 72 hours for an attack of migraine without aura, untreated or unsuccessfully treated. That window counts headache. It says nothing about when you can think clearly again.
The after-phase is well documented. ICHD-3 describes the postdrome as a symptomatic phase that follows the resolution of pain, lasting up to 48 hours, in attacks with or without aura ([source](https://ichd-3.org/definition-of-terms/)). Research on patients' own diary records has looked at this window directly, and it treats the hours after the pain stops as part of the attack, not as recovery from it.
Put those together and the forced endpoint is making a claim the literature does not support. It says the attack ended when the headache did. For many people, it didn't.
4 to 72 h
ICHD-3 duration criterion for a migraine-without-aura attack (headache phase, untreated or unsuccessfully treated)ICHD-3, International Headache Society 2018
81%
of patients in an e-diary study who logged at least one non-headache symptom after the headache resolved Thirty-three patients reported at least one postdrome symptom with their attacks, which was 79% of the patients studied. ([source](https://pmc.ncbi.nlm.nih.gov/articles/PMC8108113/))Giffin et al., Neurology 2016
One attack, recorded two ways
Take an ordinary weekday attack and log it both ways.
At 6 a.m. Tuesday you wake with a stiff neck and can't stop yawning. Pain arrives around 9. You take a triptan at 9:30, and by 1 p.m. the headache is gone. That's when the app asks for an end time, so you enter 1 p.m.
Here's what the record misses. Light still hurts through the evening. Wednesday morning you're foggy enough to reread a short message several times, and the fatigue doesn't lift until mid-afternoon. You cancel a meeting.
The forced-endpoint log says: a four-hour attack, treated, successful. The continuous record says: roughly 33 hours of symptoms from first warning sign to last, with a lost working morning on a day the tracker scores as migraine-free.
Both logs describe the same body on the same two days. Only one is true.
What gets recorded
Forced-endpoint log
Continuous timeline
Attack duration
4 hours (9 a.m. to 1 p.m.)
About 33 hours (6 a.m. Tue to mid-afternoon Wed)
Warning signs (neck stiffness, yawning)
Not attached, or not logged
Attached as the start of the attack
Residual light sensitivity
Outside the record
Logged into Tuesday evening
Next-day brain fog and fatigue
Lost, or a loose symptom with no attack link
Logged as postdrome of Tuesday's attack
Treatment result
Success
Headache relieved; function impaired into Wednesday
Wednesday
Migraine-free day
Impaired day tied to one attack
One hypothetical attack, two data models. Times are illustrative.
What changes if the attack doesn't end at pain-free
Three things in your history quietly change.
Duration shrinks. Every attack you close at pain resolution comes out shorter than the one you lived, and a year of them adds up to a picture that undersells the condition.
Treatment looks better than it is. A rescue med that clears the pain but leaves you useless until the next afternoon shows up as a clean success. That's half the story your neurologist needs when weighing whether an acute treatment is working for you.
Attack counts get muddied. When pain comes back the next morning, a closed record forces you to open a new attack, so one long episode can be counted as two. Meanwhile the impaired days in between vanish from anything you'd hand to an employer or a disability reviewer.
We think the fix is simple: stop requiring the end time. Let the episode stay open while symptoms continue, and treat 'over' as something you decide looking back, when you actually know.
A timeline that keeps recording after the pain stops
Postdrome is named after the phase most trackers leave out, and it's built around a continuous symptom timeline. The fog on Wednesday morning belongs in the same record as Tuesday's headache, and that's where it goes.
The practical pieces follow from that. Aura Mode keeps logging usable when looking at a bright screen is the last thing you want to do. Your data stays on your device, and you can export it for an appointment or a claim. Pricing is a lifetime purchase, stated up front.
None of that requires you to know when the attack ended. Log what you feel while you feel it. The shape of the attack shows up on its own.
Track the whole attack, including the part after the pain
Postdrome tracks the whole attack, not just the headache. The continuous symptom timeline keeps the after-phase (residual photophobia, neck stiffness, brain fog, fatigue) attached to the attack that caused it. Aura Mode is there for logging when screens hurt, your data stays on your device and exports cleanly for appointments or claims, and pricing is a one-time lifetime purchase that's stated up front.