Hygiène du suivi du temps avec MCP : détecter les timers longs et les trous
Maintain clean time tracking data using MCP. This operational playbook shows you how to check current tracking status, flag timers running too long, identify tracking gaps, and propose cleanup steps—with optional timer stopping after explicit approval.
Ce que ce workflow permet
Time tracking hygiene with MCP ensures accurate time logs:
Résultats clés
- Status monitoring: Check current tracking status across workspace
- Anomaly detection: Flag timers running too long (e.g., >8 hours)
- Gap identification: Find periods with no time tracking
- Cleanup proposals: Get AI-suggested actions to fix issues
- Data quality: Maintain accurate time tracking records
Prérequis
Before using this workflow, ensure you have:
- Corcava MCP server configured in your AI assistant
- API key with read access to time tracking
- Time tracking data in your workspace
- For stopping timers: API key with write permissions
Workflow pas à pas
Step 1: Check Current Tracking Status
Start by checking what timers are currently running:
Status Check Prompt
What the AI does:
- Calls
get_tracking_statusto check active timers - Retrieves task details for tracked tasks
- Calculates duration for each timer
- Presents status summary
Step 2: Flag Long-Running Timers
Identify timers that have been running too long:
Long-Running Timer Detection Prompt
What the AI does:
- Analyzes timer durations
- Flags timers exceeding thresholds
- Identifies likely forgotten timers
- Proposes cleanup actions
Step 3: Detect Tracking Gaps
Find periods with missing time tracking:
Gap Detection Prompt
What the AI does:
- Analyzes time tracking history
- Identifies days with no entries
- Finds gaps in tracking patterns
- Presents gap analysis
Step 4: Propose Cleanup Steps
Get recommendations for fixing issues:
Cleanup Proposal Prompt
What the AI does:
- Analyzes all identified issues
- Proposes specific cleanup actions
- Prioritizes urgent items
- Presents cleanup plan for review
Step 5: Stop Long-Running Timers (Optional, with Approval)
⚠️ Always Confirm Before Stopping Timers
When stopping long-running timers:
- Preview First: Show which timers will be stopped
- Confirmation Token: Require "CONFIRM" or "STOP ALL" before stopping
- Review Impact: Understand what time will be logged
Safe Timer Stopping Prompt
What the AI does:
- Shows timer details
- Waits for "STOP TIMER" or "CONFIRM"
- Only after confirmation, calls
stop_time_tracking - Confirms timer was stopped
Complete Workflow Prompts
Here are complete, copy-paste ready prompts:
Full Hygiene Check
Use this when: You want a complete hygiene audit
Quick Long-Running Timer Check
Use this when: You just want to check for forgotten timers
Workflow Variants
Variant 1: Team-Wide Hygiene Check
Check hygiene across the entire team:
What happens: AI analyzes tracking hygiene for entire team
Variant 2: Daily Hygiene Routine
Regular daily check:
What happens: AI performs quick daily hygiene check
Example: Complete Hygiene Check Session
Here's a real example of how a hygiene check session flows:
User Prompt
AI Response (Hygiene Report)
Time Tracking Hygiene Report
Active Timers (1 found):
- Task: "Implement user authentication" - Running for 14 hours (started yesterday at 3:00 PM)
⚠️ Long-running timer detected
Recommendation: This timer has been running for 14 hours. Likely forgotten. Should be stopped.
Tracking Gaps:
- No tracking entries on Jan 22, 2026 (gap detected)
- No tracking entries on Jan 24, 2026 morning (9 AM - 12 PM gap)
Cleanup Recommendations:
- Urgent: Stop the 14-hour timer on "Implement user authentication"
- Optional: Add retroactive time entries for Jan 22 if work was done
Safety Patterns
⚠️ Confirmation Rules for Stopping Timers
When stopping long-running timers:
- Always preview: Show timer details before stopping
- Require explicit confirmation: Use "STOP TIMER" or "CONFIRM" token
- Review impact: Understand what time will be logged
- Verify task: Confirm you're stopping the correct timer
Troubleshooting
No Issues Found
Symptom: AI reports no hygiene issues
Possible causes:
- Time tracking is actually clean
- Thresholds too high (e.g., only flagging >24 hours)
Fix: Adjust thresholds: "Flag timers running more than 4 hours"
Too Many Issues
Symptom: Hygiene check shows many problems
Possible causes:
- Many forgotten timers
- Team not using time tracking consistently
Fix: Focus on urgent items: "Show only timers running more than 12 hours"
Related Tools
This workflow uses these Corcava MCP tools:
get_tracking_status
Check current timer status
stop_time_tracking
Stop long-running timers
list_tasks
Find tasks with tracking issues
Related Use Cases
Time Tracking Basics
Learn basic time tracking workflows
Risk Review
Include tracking hygiene in risk reviews
Maintain Clean Time Tracking
Connect your AI assistant to Corcava and keep time tracking data accurate
