> For the complete documentation index, see [llms.txt](https://teranoapps.gitbook.io/missing-worklog-reminder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teranoapps.gitbook.io/missing-worklog-reminder/usage/reminder-check-runs.md). # Reminder Check Runs #### Inspect execution history for a single reminder The **Reminder Check Runs** dialog shows the **full execution history** of a single reminder policy.\ Where the **Reminder report** focuses on trends and user-by-day matrices, this view lets you see: * When exactly the reminder was executed * Which rule and reporting window were used * How many users passed or failed in that specific run It’s designed for **project managers, administrators, and team leads** who need to verify that reminders run as expected, troubleshoot configuration changes, or inspect a particular check in detail.\ Individual users still only see their own outcomes in **My Worklog Reminders**. *** #### 🎥 Interactive Demo: Reminder Check Runs in Action Watch a short demo to see how to open the **Reminder Check Runs** dialog, read the execution list, and drill down into the user details for a single run. This interactive preview shows: * How each run is added to the list with time, rule, window, and summary * How compliance summaries are updated after each policy check * How managers can open **User Compliance Details** to verify logged hours per user and per window {% @arcade/embed flowId="2XU2LFlinaJeuQf7XKs7" url="" %} #### 📊 Accessing the Run History You can open the run history directly from the reminder configuration view. 1. Go to **Worklog Reminders**. 2. Find the reminder you want to inspect. 3. Click **View check history**. A dialog opens titled for the selected reminder and lists all recorded runs.

Reminder check history.

*** **🕓 Understanding the Runs** Each row in the results table represents one completed or attempted reminder run. **Executed at**\ Shows the exact date and time the reminder policy was executed. **Rule**\ Displays the rule logic applied during that run (e.g. *Weekly ≥ 6 days*, *Weekly ≥ 2 days*).\ This corresponds directly to the threshold defined in your reminder configuration. **Window**\ Indicates the reporting period that was analysed — for example, *13 – 19 Oct 2025*.\ This tells you which worklogs were included in the evaluation. **Compliance summary**\ Shows how many users met the policy versus how many didn’t.\ Examples: * *22 errors* — all users failed the requirement. * *1 / 22 success* — only one user met the target. * *Success* — all users were compliant. Each summary may also include quick indicators (avatars or icons) representing the evaluated users. *** **🔍 Viewing User-Level Details** Select **Details →** on any row to drill down into **User Compliance Details**.\ This view lists every user or group included in the policy and their compliance result for the selected window.
**What you’ll see:** * User avatars and display names. * Compliance outcome (e.g. *0 h logged*, *success*, *error*). * A consistent visual tag that helps you quickly identify missing logs. This level of visibility allows managers to verify exactly **who** fell below the required threshold and **how much time** is missing. *** **🧭 Typical Manager Workflow** 1. Open the reminder’s **View results** dialog. 2. Review the latest execution summary to see overall compliance. 3. Click **Details** to inspect specific users who failed the rule. 4. Follow up with teams if needed, or adjust thresholds and schedules to better fit working patterns. *** **👥 Manager vs. User Views** * **Reminder report** * Full-page view * Shows trends over time and a matrix of **users × days/weeks/months** * Great for monitoring overall health of a policy and exporting data * **Reminder Check Runs** * Dialog view * Shows **each individual execution** of the reminder * Ideal for debugging, validating rules, and reviewing a single check in detail * **My Worklog Reminders** * End-user dashboard * Shows only personal reminders and lets users **resolve** or **ignore** them Together, these two perspectives give both managers and employees full transparency — ensuring that policies are enforced fairly and everyone can stay compliant. *** **▶️ Next: My Worklog Reminders** See the end-user view of reminders. Learn how teammates open their **My Reminders** page, review active escalations, jump to time tracking, and **resolve** or **ignore** items. This section also explains the personal history view, what changes when a reminder is resolved, and how exhausted reminders stop showing in-product flags. --- # 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://teranoapps.gitbook.io/missing-worklog-reminder/usage/reminder-check-runs.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.