I discovered this while load-testing the incident response plugin. This behaviour is documented however it is more pronounced while load-testing and haven't been observed in production yet.
The root cause of the issue is that the plugin does not update `all_headers` atomically because of which it sometimes overwrites the previous value that may be updated concurrently. This is a known limitation of the KVStore.Set API, which is why `KV.Set` with KVOptions was introduced.
This issue may become irrelevant if plugin switches to using database directly.
Steps to reproduce:
1. Clear out plugin db
2. Use load-testing tool to start stress testing the plugin