How do I troubleshoot WorkPoint aggregation failures caused by SharePoint list throttling, fix the underlying query, and get notified when these jobs fail?

A: When your WorkPoint aggregation job runs, you might see a log entry like:

Update aggregations entity id: [EntityID], on list id: [ListID]

followed by these errors:

• WorkPoint: “Both the aggregation list and the aggregation field was found, but something went wrong. This may be due to a invalid query.”

• SharePoint: “The attempted operation is not permitted because it exceeds the list view threshold.”

This happens because SharePoint Online enforces a 5,000-item list view threshold, blocking any CAML query that would scan or return more items than this limit.

To resolve the aggregation failure:

1. Index your filter fields
   Ensure every <FieldRef> used in your <Where> clause points to a column that’s indexed, so SharePoint can locate items without scanning the entire list.

2. Remove any <Or> operators
   OR statements force full-list scans and will always trigger throttling on large lists.

3. Limit the total returned items
   Rewrite or split your query so it never attempts to return—or even evaluate—over 5,000 items. Test your CAML via the REST API or PowerShell to confirm it stays below the threshold before running the aggregation.

To get proactive email notifications when a job fails:

1. Navigate in the WorkPoint 365 admin interface to WorkPoint Event Logging.

2. Click Alert Settings.

3. Enter the e-mail address of the recipient (must be a registered user on the solution).

4. Select the “Data aggregation” (or other) job types to monitor, then click Add and Save.

5. Finally, in Scheduled Jobs, create or verify an Alert Job is scheduled at your chosen interval—this job is responsible for sending the notification e-mails (support.workpoint.dk).

With these steps, you’ll both eliminate the root cause of your aggregation errors and be immediately informed by e-mail if any future failures occur.