Short answer: Ask ARIA to “show my previous scans” or “pull up my history.” ARIA automatically accesses your inspection history from the cloud. Free users see a summary (session count, vehicles, date range). 👑 Premium users get full analysis with the ability to compare current issues against past sessions.
What is Scan History?
Every time you connect OBDAI to a vehicle and run a successful diagnostic session, the app saves a snapshot to your account:
- Vehicle info: VIN, year, make, model
- Diagnostic data: Trouble codes detected, MIL status, monitor readiness
- Session details: Date, time, device used, connection type
- AI interactions: Whether you used ARIA during that session
This data is stored securely in the cloud and tied to your account — so you can access it from any device where you’re logged in.
How to Access Your History
Option 1: Ask ARIA (Recommended)
Just ask ARIA in natural language:
- “Show my previous scans”
- “Pull up my history”
- “What scans have I done?”
- “Show history for this vehicle”
- “When did I last scan my F-150?”
- “Compare this to my last scan”
ARIA automatically calls the getPreviousInspections() function, which retrieves your sessions from the cloud.
Option 2: Use Suggestion Chips
After any diagnosis, look for chips like:
- “👑 Compare with history”
- “Show previous scans”
- “What did I find last time?”
Tapping these triggers ARIA to pull your historical data.
What You’ll See
Free Users: Summary Only
If you’re on the free tier, ARIA shows you a high-level summary:
📊 Your Inspection History
You have 12 sessions saved across 3 vehicles:
• 2016 Cadillac Escalade — 8 sessions (last: Dec 15)
• 2019 Ford F-150 — 3 sessions (last: Nov 28)
• 2014 Honda Accord — 1 session (Oct 3)
👑 Upgrade to Premium to analyze inspection history and track trends.
This tells you that history exists without revealing the detailed data.
👑 Premium Users: Full Analysis
Premium unlocks the complete picture:
- Full session data — DTCs, sensor readings, timestamps
- Comparison analysis — “This P0420 also appeared on March 15 and June 2”
- Pattern detection — “Your fuel trims have been drifting positive for 3 months”
- Deep dive capability — “Show me the raw data from that June session”
Example:
“Your P0171 code appeared twice before:
- March 15: Cleared after MAF cleaning
- June 2: Returned with +18% LTFT
- Today: Still present with +22% LTFT
The fuel trim trend suggests the underlying issue wasn’t fully resolved. The vacuum leak theory we discussed in March is looking more likely.”
How History Helps Your Diagnosis
1. Recurring Problems
ARIA can spot codes that keep coming back — helping identify whether a repair actually worked or if the problem is deeper.
2. Trend Analysis
Over multiple sessions, ARIA tracks whether sensor readings are getting worse, staying stable, or improving.
3. Repair Verification
After a repair, scan again. ARIA compares pre-repair and post-repair data to confirm the fix worked.
4. Vehicle Health Timeline
See how your vehicle’s health has changed over months — useful for maintenance planning or when considering selling.
Requirements for History to Work
You Must Be Logged In
History is tied to your account. Anonymous users don’t have history saved.
If ARIA says “User not authenticated,” tap the account icon (top right) and sign in.
Sessions Must Connect Successfully
Only successful diagnostic sessions are saved. If a session fails to connect to the vehicle, no history is recorded.
Vehicle Needs a VIN or Identifier
Sessions are grouped by VIN. If the VIN wasn’t captured during a session, that session appears as “Unknown Vehicle” in your history.
⚠️ Always Disconnect Before Closing the App
This is important: Your detailed second-by-second sensor data uploads to the cloud when you tap Disconnect. If you skip disconnecting and just close the app, that upload may not complete — which means ARIA won’t have the full data record for that session.
Best practice:
- Finish your diagnostic session
- Tap Disconnect and wait for the “Disconnected” confirmation
- Then close the app
If you frequently close the app without disconnecting, you may notice ARIA saying “no detailed data available” for past sessions even though you remember running them. The session metadata might exist, but the rich sensor data that powers deep analysis could be missing.
Filtering History
You can ask ARIA to filter by vehicle:
- “Show history for VIN 1G1YY22G955101234”
- “Previous scans on my Cadillac”
- “Just show my F-150 sessions”
ARIA passes these filters to the backend, returning only matching sessions.
Troubleshooting
“I asked for history but ARIA says I have none”
- Are you logged in? Tap the account icon to verify.
- Did previous sessions connect? Failed connections don’t save history.
- Same account? History is tied to your login. If you used a different account before, those sessions won’t appear.
“I see sessions but not the data I expected”
- Free tier? You’ll only see the summary. Upgrade to Premium for full data.
- VIN mismatch? If the VIN wasn’t captured, sessions appear under “Unknown Vehicle.”
“ARIA isn’t showing the comparison I asked for”
Try being specific:
- ❌ “Compare this” (too vague)
- ✅ “Compare this P0171 to my previous scans”
- ✅ “Did this code appear before?”
Privacy & Data
Your inspection history is:
- Tied to your account — Only you can access it
- Stored securely — Azure cloud with encryption
- Not sold or shared — We don’t share your vehicle data with third parties
- Deletable on request — Contact support@obdai.app to request deletion
Related Articles
Questions? support@obdai.app