> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/managing-subscriptions/the-subscription-activity-timeline.md).
# The Subscription Activity Timeline
Use the Subscription Activity Timeline to see every event on a subscription contract: payments, edits, customer actions, and Klaviyo triggers.
Every subscription contract has a Timeline panel on its detail page, a chronological audit trail of every event for that contract. Use it to answer "what happened with this subscription?" without leaving the contract page.
The Timeline records who did what, when, and why. It's the source of truth for subscription history.
#### Where to find it
In Manage Subscriptions, open any contract. The Timeline panel sits on the right side of the page, alongside Customer, Loyalty Points, Shipping address, and Payment method.
By default the timeline shows the most recent 5 events. Click to expand the full history.
#### What gets recorded
Every meaningful event on a subscription is logged. Categories:
**Contract lifecycle**
* Subscription created (with the originating order reference)
* Status changes: paused, resumed, cancelled, marked Failed
**Billing and payments**
* Each scheduled billing attempt: success or failure
* Manual charges from Order Now
* Each dunning retry attempt and its outcome
* "All retries exhausted" event
**Modifications**
* Frequency changes
* Next-billing-date changes
* Product additions, removals, swaps, quantity changes
* Shipping address updates
* Payment method updates
**Notifications**
* Upcoming-order reminders sent to the customer
* Subscription-created confirmations
* Payment-failed notifications
* Delivery-failure alerts
**Klaviyo triggers**
* When a Roadmap Klaviyo metric (e.g., Roadmap Upcoming Order) fires for a billing cycle, the trigger is logged here. Useful for confirming a flow ran for the cycle you expected.
#### Who triggered each event
Each event records the actor. Categories you'll see:
| Actor | What it means |
| -------------- | ------------------------------------------------------------------------------ |
| Customer | The customer took the action from their account page |
| \[admin email] | A specific admin took the action from the Roadmap admin |
| Roadmap | An automatic system action (scheduled billing, dunning retry, Klaviyo trigger) |
Knowing the actor is often the most important part of the event. It tells you whether the customer chose this or whether the system did it.
#### How events look
Each event shows:
* an icon indicating the category
* a short description (e.g. "Order #1032 was placed manually.")
* the timestamp
* the actor
Examples from a real Timeline:
* "Order #1032 was placed manually." by an admin, from Order Now
* "Customer skipped delivery #3." by the customer, from their account
* "Next delivery date changed to 8 Apr 2026." by an admin
* "Klaviyo: Roadmap Upcoming Order metric triggered for billing cycle 3" by Roadmap, automatic
* "Payment method was updated." by an admin
#### Best way to use the Timeline when troubleshooting
When a customer asks something like "why was I charged on this date?" or "I thought I'd cancelled":
{% stepper %}
{% step %}
Open the contract
In Manage Subscriptions, find the customer's contract.
{% endstep %}
{% step %}
Open the Timeline panel
Expand it to show the full history.
{% endstep %}
{% step %}
Find the event in question
Match the customer's complaint to an event: a charge, a status change, a modification.
{% endstep %}
{% step %}
Read the actor and reason
If the actor is Customer, the customer triggered the action themselves (they may have forgotten).
If the actor is Roadmap, the system did it on schedule. Check the dunning state, the billing date, or the Klaviyo trigger.
If the actor is an admin, that admin took the action manually. Check with them if you don't know why.
{% endstep %}
{% endstepper %}
#### Existing subscriptions before the feature shipped
The Timeline includes backfilled events for contracts that existed before the feature went live. Backfilled events use the original timestamps where Roadmap has them. For older events where the exact time isn't known, dates are approximated.
If a Timeline looks sparse on older events, that's why; new events going forward record everything in real time.
#### Common Timeline reads
**"I thought my subscription was cancelled"**
Look for a Subscription cancelled event. If you don't see one, the contract is in another status, likely Paused or Failed.
**"I was charged but didn't get an order"**
Find the billing event for that date. If it's there with status Failed, the customer wasn't charged successfully. If it's Succeeded, look for a corresponding Order created event nearby.
**"Why didn't my Klaviyo flow trigger?"**
Find the Klaviyo: ... metric triggered event for the relevant billing cycle. If it's there, the metric fired. The issue is downstream in Klaviyo. If it's not, Roadmap didn't fire the metric for that cycle.
#### Related guides
* Subscription statuses explained
* The Manage Subscriptions admin: a tour
* Failed payment retries (dunning)
* Editing a customer's subscription
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.roadmap.so/subscriptions/managing-subscriptions/the-subscription-activity-timeline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
