40 lines
2.0 KiB
Markdown
40 lines
2.0 KiB
Markdown
# ConnectWise Schedule Entries Bug — Session Notes
|
||
|
||
## Bug Summary
|
||
The `/schedule/entries` endpoint is **non-functional** for retrieving current/future calendar data. It returns a static mirror of historical entries from 2011–2012 regardless of date filters.
|
||
|
||
## Reproduction Steps
|
||
1. Query: `GET /schedule/entries?conditions=member/id=<memberId>`
|
||
2. Result: Returns ~200 entries, all dated 2011-12-12 through 2012-03-27.
|
||
3. Add date filter: `conditions=member/id=<memberId> and dateStart>[2026-08-09T00:00:00Z]`
|
||
4. Result: **Empty response** (no entries at all).
|
||
5. Query by ticket ID: `conditions=objectId=121247`
|
||
6. Result: **Empty response** (no schedule entries returned for known active ticket).
|
||
|
||
## Attempted Workarounds (All Failed)
|
||
| Approach | Result |
|
||
|----------|--------|
|
||
| General list with `member/id` | Returns 2011 data |
|
||
| Date range filter `dateStart>[...]` | Empty response |
|
||
| Date range filter `startDate>[...]` | Empty response |
|
||
| Ticket-linked query `objectId=<id>` | Empty response |
|
||
| `pageSize=1000` | No effect on date filtering |
|
||
| Different member IDs | Same behavior |
|
||
|
||
## Server Response Characteristics
|
||
- The API returns HTTP 200 with a valid JSON array.
|
||
- No error codes or status messages indicating a problem.
|
||
- The data is simply wrong (stale by ~14 years).
|
||
|
||
## Impact
|
||
- **Cannot retrieve current calendar/schedule data via REST API.**
|
||
- No known programmatic workaround exists.
|
||
- Technicians must use the ConnectWise web UI or desktop client for calendar access.
|
||
|
||
## Alternative Data Sources Tested
|
||
- **Nextcloud CalDAV**: Successfully queried personal calendar (`/remote.php/dav/calendars/scott/personal/`). Returns actual current events. Requires separate credentials.
|
||
- **ConnectWise Activities (`/sales/activities`)**: Tested but returned empty results for date ranges.
|
||
|
||
## Recommendation
|
||
Do not attempt to build automation around `/schedule/entries` for current calendar data. Treat this endpoint as **read-only historical reference** until ConnectWise fixes the bug.
|