autodesk forge – Intermittent spike (~14k) of BIM 360 webhook notifications on a single day

We are seeing intermittent, unexplained spikes in BIM 360 webhook notifications, where ~10k–14k file-related events are received within a single day, with otherwise normal traffic before and after. These notifications are primarily Design Automation completion or failure events, which appear to be triggered when a file change is detected in BIM 360, but there is no explanation for the number of notifications received.

Table of Contents

What we’re seeing

Occurrences:

Mid-September: ~14k notifications in one day
Nov 19: similar spike
Dec 9: ~14k notifications in one day
No occurrences so far in Jan or Feb

Observations

Appears related to file change events
Happens once in the month, on a single day

Questions

Are there known Autodesk/BIM 360 background processes that can trigger large batches of webhook events?
Can certain lifecycle actions (publish, indexing, permissions sync, version reconciliation, etc.) re-emit file change notifications?
Has anyone seen periodic or monthly webhook spikes like this?
Any recommended way to trace a spike back to a specific triggering action or system process?

We are starting to log full webhook payloads to identify which subscription or event type is responsible, but wanted to check if this is known or expected behavior.

Any insights appreciated.