---
id: "8f452856-eb1e-44f6-b95d-4ea7e804bfda"
name: "Canvas Planner"
micro_summary: "Extract assignments from Canvas dashboard planner — stable selectors, DOM structure, traps"
status: "resolved"
see_also: []
scope: "Canvas LMS dashboard planner — extracts upcoming assignments, announcements, discussions grouped by day and course from the dashboard. Covers stable selectors, DOM structure, URL patterns, text patterns, and traps. Only works on the dashboard (/), not on /courses/#/assignments."
warnings: "React SPA: always wait_for_load() + wait(1) for hydration. Never trust window.prefetched_xhrs — they're unresolved Promises.\nPlanner overrides are UI/to-do cleanup only; they do not submit assignments or create grades. For point-bearing work, require independent submission/grade evidence before clearing duplicate/dead cards."
---
## URL patterns

- Dashboard (planner lives here): `https://<school>.instructure.com/`
- Course page: `https://<school>.instructure.com/courses/<course_id>`
- Assignment page: `https://<school>.instructure.com/courses/<course_id>/assignments/<assignment_id>`

**Prerequisite:** navigate to the dashboard (`/`). The planner only exists there.

## DOM structure

```
#dashboard-planner
  └─ .planner-day                     (one per day with items)
       ├─ h2 > div[data-testid="today-text"]    "Today"/"Yesterday"/day name
       ├─ h2 > div[data-testid="today-date"]    "May 3"
       └─ .planner-grouping            (one per course)
            ├─ .Grouping-styles__hero  (course link)
            ├─ .Grouping-styles__title (course name)
            └─ .planner-item           (one per assignment)
                 ├─ input[data-testid="planner-item-completed-checkbox"]
                 ├─ .PlannerItem-styles__type   "COURSE NAME ASSIGNMENT"
                 └─ a[data-cid="Link"]          (assignment link)
                      └─ span                   "Assignment name, due ..."
```

## Stable selectors

| Selector | Purpose |
|----------|---------|
| `#dashboard-planner` | Root container |
| `.planner-day` | Day section |
| `.planner-grouping` | Course grouping |
| `.planner-item` | Individual item |
| `[data-testid="planner-item-completed-checkbox"]` | Completion checkbox |
| `[data-testid="today-text"]` | Day label |
| `[data-testid="today-date"]` | Date string |
| `a[data-cid="Link"]` | Assignment/course link |
| `.PlannerItem-styles__score` | Points (e.g., "100 pts") |

## Fragile selectors

CSS module classes that CAN change: `.css-bbpeg1-view-heading`, `.Grouping-styles__*`, `.PlannerItem-styles__*`. Prefer stable selectors above.

## Item types

`.PlannerItem-styles__type` text is `"<COURSE NAME> <TYPE>"` where TYPE: Assignment, Announcement, Discussion, Submission.

## Text patterns

- Link text: `"Assignment <name>, due <day>, <Month> <day>, <year> <time>."`
- Strip `"Assignment "` prefix, split on `", due "` for name + due date
- Course title: from `.Grouping-styles__title` text
- Day label + date: from `h2` child divs

## Traps

1. Prefetched XHRs (`window.prefetched_xhrs`) contain unresolved Promises — cannot parse. DOM extraction is the reliable path.
2. "Load more" pagination: planner shows ~2-3 weeks upfront. Screenshot to check for more.
3. Empty day ranges: `.planner-empty-days` have no `.planner-grouping` children. Skip them.
4. React SPA: use `wait_for_load()` + `wait(1)` for hydration.
5. Multi-item days: iterate `.planner-grouping` → `.planner-item`, never assume one item per day.

## API endpoints (for future HTTP use)

- `/api/v1/planner/items?start_date=<ISO>` — planner items
- `/api/v1/users/self/missing_submissions?...` — overdue items

## Helper functions

Call after navigating to the Canvas dashboard:
- `canvas_get_assignments()` — extract all visible planner items. Returns list of dicts: day_label, date, course, course_url, name, due, url, type, completed.
- `canvas_get_weekly_assignments(days=7)` — filter to next N days (default 7).

---

### 2026-06-07 00:41 UTC

## 2026-06-06 — Marking non-submission planner Page items complete

For Canvas planner-only grunt items (for example `plannable_type: wiki_page`) the Dashboard checkbox may miss items after React removes completed cards. The API path works with browser cookies:

```js
await fetch('/api/v1/planner/overrides', {
  method: 'POST',
  credentials: 'same-origin',
  headers: {'Content-Type': 'application/json', 'X-CSRF-Token': ENV.CSRF_TOKEN},
  body: JSON.stringify({plannable_type: 'wiki_page', plannable_id, marked_complete: true})
})
```

Use only for non-submission planner tasks (Pages/admin items). Do not use this to fake completion of assignments, discussions, quizzes, or external tools.

---

### 2026-06-07 00:57 UTC

## 2026-06-06 — IBUS planner cleanup evidence

Safe planner-only cleanup was performed through `/api/v1/planner/overrides` with browser cookies:

- Non-submission wiki pages and announcements were marked complete via `marked_complete: true`.
- Zero-point `International Business eBook` assignment (`855010`, `points_possible: 0`) was launched to the McGraw Hill coversheet, then its planner card was marked complete; Canvas submission remained unsubmitted, as expected for a no-point resource.
- Dead duplicate SmartBook stub cards (`855030`, `855021`) were marked complete only after same-script verification that the real direct SmartBook records (`857287`, `857288`) were `graded` with score `100`.

Guardrail: for point-bearing assignments, never use planner overrides as a substitute for actual submission/grade evidence. Only use them to clear known duplicate/dead planner cards after independent grade verification.