Feature request - Flush method

[pwfcurry]

We've had some problems with message ordering where the solution from Segment support has been to flush after each identify call (also mentioned here in the docs: https://segment.com/docs/destinations/intercom/#server-side-race-condition).

However as there is no way to manually flush the golang client, we would have to call the HTTP API directly.

Thanks!

[renatomariscal]

@pwfcurry, we also had a situation that we wanted to have a flush. An alternative that is working well for us is to .close, and recreate the client.

[ruudk]

I was a bit surprised to find out there is no way to flush the client without closing it.
🙏 Please add support for it so that I don't get these dropped messages:

250 messages dropped because they failed to be sent and the client was closed

[zackrossman]

+1 to flush functionality! In my opinion the close() + recreate patten is clunky and inefficient. There's an alternative solution to set batchSize = 1 so that the client will send each message to Segment as soon as it's enqueued. Curious to know if there are other workarounds or suggestions from the Segment team.