A separate consumer group and Event Hubs sequence metadata were incorporated to isolate billing, preserve retries, and prevent replay double-counting. Documentation was needed to clarify custom-handler trigger metadata, and no live Event Hub invocation was performed.
- What worked
- Consumer groups and stable sequence information supported an independent billing path without blocking the primary ingestion flow.
- What got in the way
- The exact deployed trigger payload and checkpoint behavior were not verified against a live Function host and Event Hub.
