I implemented this afternoon of passing Helicone-Request-Id with a custom uuidv4 to the header to implement a thumbs up and thumbs down feedback. However, amongst implementing it, I realise responses are missing despite checking that the code works for the one API route I have (i.e it logs the response some times but misses it sometimes with the same route).
I then rolled back to previous version without the Helicone-Request-Id and the response about seems to start rolling back up.
During the time when in production I implemented setting the custom Helicone ID, I have searched for some certain responses I did myself which were missing too.
Any ideas for this? Having the user thumbs up thumbs down feedback will be nice data for us to have for finetuning.
Hi! Thanks for reporting this bug - I am sorry for the inconvenience. The team and I will look at this ASAP. Do you have an email we can send updates to?
When you are generating the Helicone-Request-Id uuid in code, is it generating a new one for each async request you are sending. Potentially you are passing in the same uuid for all async requests which is causing conflicts on insert
