Gitlab Webhook and slow consumers

I am noticing that the Gitlab Pipeline Webhook seems to omit changes when my service is slow at processing it. E.g. of events 1, 2 and 3 (all for the same pipeline), event 3 is ready to be sent before my service finishes with 1. When it’s done, it received 3 next, without having heard about 2. Is this a feature? While I welcome this behavior, I’m not seeing it being documented anywhere, so I am not sure if I should expect it.

Turns out my observation was wrong. Gitlab does every event immediately. It merely appeared to me as if it didn’t because it only does so strictly when the status of the pipeline (not job) has changed. For job updates one would need to use Job Webhook as well.