Live-Blog Staleness
Measure live-blog update age against a supplied staleness threshold.
Description
Live-blog staleness is the elapsed time since a supplied last update.
Live-blog staleness is the elapsed time since a supplied last update. A caller maximum defines the stale boundary.1
Measure live-blog update age against a supplied staleness threshold.
When to use Live-Blog Staleness
Use this tool to measure live-blog update age against a supplied staleness threshold.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Live-Blog Staleness and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter lastUpdatedAt, asOfAt, staleAfterMinutes using the field table and calculation rules, then run the tool.
- Read ageMinutes, minutesBeyondThreshold, stale. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| lastUpdatedAt | Last update timestamp | string | Required |
| asOfAt | As-of timestamp | string | Required |
| staleAfterMinutes | Staleness threshold (min) | number; minimum: 0 | Required |
Enter valid, chronologically ordered parseable timestamps and nonnegative maximum minutes. Return age, clipped excess and strict stale flag; equality is current. Use timestamps with explicit offsets.
ageMinutes=(asOf−lastUpdate)/60,000; stale=age>maximum Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| ageMinutes | Update age (min) | number; minimum: 0 |
| minutesBeyondThreshold | Minutes beyond threshold (min) | number; minimum: 0 |
| stale | Update is stale | boolean |
{
"input": {
"lastUpdatedAt": "2025-01-01T12:00:00Z",
"asOfAt": "2025-01-01T12:45:00Z",
"staleAfterMinutes": 30
},
"output": {
"ageMinutes": 45,
"minutesBeyondThreshold": 15,
"stale": true
}
}Limitations and assumptions
No blog is fetched, current clock sampled or new post detected; native date parsing controls accepted formats.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Live-Blog Chronology Sorter: Sort timestamped live-blog entries in a caller-selected chronological direction. For a complementary task, use Subscriber Sunset: Measure subscriber access sunset timing against a supplied allowance.
References
-
Live-Blog Staleness — tool.io
Similar or alternative tools
- Live-Blog Chronology Sorter
Sort timestamped live-blog entries in a caller-selected chronological direction.
- Subscriber Sunset
Measure subscriber access sunset timing against a supplied allowance.