Link to this headingWhy We Built This

When you create automations, they run in the background every time you upload an activity. But there was no way to see:

• Did my automation actually run?
• Which rules matched?
• What did each rule change?
• Why didn't my automation trigger?

The history page shows a list of executions, but it's hard to visualize patterns or quickly check specific days. I wanted a monthly view where I could see all my activities and click any day to check what automations did.

That's why we built calendar view. It's basically an execution log with a calendar interface.

Link to this headingWhat You See

The calendar displays a monthly grid with your activities. Each day shows:

• Activity names (after automation processing)
• Multiple activities if you did more than one workout

Click any day and a sidebar opens showing:

• Which automations matched that activity
• What actions each automation applied
• Execution order (which ran first, second, etc.)
• Whether any automation used the "stop" flag
• Success/failure status

That's it. Simple execution tracking in a calendar format.

Link to this headingWhen It's Useful

Debugging: Your automation didn't work as expected? Open the calendar, click the activity, see exactly which automations ran and what they did.

Verification: After creating a new automation, check the calendar to confirm it's working on your activities.

Understanding interactions: When you have multiple automations, the calendar shows you how they layer together—useful for catching conflicts.

Quick overview: Scan the month to see if activity names look correct. Missing weather emojis? Commutes not tagged? Calendar makes patterns obvious.

Link to this headingHow to Use It

1. Go to Calendar in the main menu
2. You'll see the current month with your activities
3. Click any day that has activities
4. Sidebar opens showing automation execution details
5. Use arrows to navigate between months

No configuration needed. If you have activities and automations, the calendar will show execution history.

Link to this headingExample: Debugging a Weather Emoji

Let's say you have an automation that adds weather emoji to activity names, but today's run doesn't have one.

Without calendar:

• Go to history page
• Search through list for today's activity
• Click to see details
• Figure out what happened

With calendar:

• Open calendar (already showing current month)
• Click today
• Sidebar shows: "Weather automation: Matched ✓, But weather data unavailable"
• Now you know why it didn't work

Faster and more visual.

Link to this headingTry It Out

Calendar view is live now. If you have automations running, go check it out and see what your rules have been doing over the past weeks.

It's a tool for understanding and debugging your automations—nothing more, nothing less.