I guess when you are sending these objects you send them as a JSON object? I would suggest that when you execute the microflow that sends this object, you set the time to the %CurrentDateTime% (https://docs.mendix.com/refguide/datetime-handling-faq). This should set the timestamp to the current Unix timestamp (which is, if I'm correct, down to the millisecond). The time difference between setting that timestamp and sending it out should be negligible.
Hi
Yes the object has an attribute (Send Time) which has the time in it that we need send the object.
The object needs to be sent at that exact time.
Thanks
A naive implementation could be:
The time might not be exact, due to conversion from object to JSON, time required to set up the connection etc, but it should be close enough. You can play around with the Delay timing, or you could create the request before you start delaying.
[Update]
Based on the volume, I would use a queue module from the appstore. The basic setup remains the same:
Could this lock the system up?
We could have 27 a second going at the most.