Comment 1 for bug 1322452

Allison Miller proposed:

"""
After some discussion, the most thorough solution we have come up with is
adding 'exported' flags to Magento objects. This eliminates the risk of
entirely missing records, as they can always be caught on the next import.
 For objects that get updated (products, for example) this flag would have
to be reset when updates occur. This will make upgrading existing
instances of the connector a bit tricky, because flags would have to be
properly set initially in Magento after the column is created.

Some other solutions we discussed but did not like are:
- Adding 'committed_create_at' and 'committed_update_at' columns to Magento
objects in the database that are set by MySQL so they reflect times more
accurately. We would still run into a possible millisecond misalignment
here.
- Adding a buffer to import times (for example, if the last job finished
searching at 09:15:00, the next would start at 09:14:30). This would not
fix the problem but it would eliminate virtually all skipped records. With
this approach, duplicate orders would have to be handled differently so
failed jobs would not need to be cleaned up regularly.
"""