Maintain changes in database via generic approach triggers into history table

Our main system database has temporal tables These have helped us hugely in working out issues However. A drawback of this is that an issue with doing a lot of updates at once can lead to a an error about not being able to update the temporal table due to the time being earlier than the period start time for the affected records I get this error when updating the database through entity framework core I need a solution where I can get a temporal table like audit but any issues do not ever get back to the system and stop a transaction from happening Can anyone suggest a solution? Has anyone tried a trigger based fix? This is using azure Sql In a perfect world our replica database would get the changes and then write to a temporal table but I’m assuming that’s not an option as I would assume that the whole structure of the source and replicated database have to be identical Paul