Jira Connector: when a sync with Jira throws an error, an invalid entry is created on tblRequestsAudit table

Issue Summary

For each action that happens on a Feature, an entry on the tblRequestsAudit is created, with the most last one having the _ValidTo set as NULL. So whenever a new entry is created, the last one is updated with a valid date, and the most recent one keeps the NULL. The problem is that, if for some reason a sync error happens, the last 2 entries on the table will keep the value as NULL.
This is reflected on EI, as the table Feature History will have the have 2 entries with the field Valid_to as 9999-12-31T00:00:00

Steps to Reproduce

1. Create a Feature on JA, let it sync with Jira
2. Break the sync between the 2 (in my case I did change one field, the PI one, as mandatory on Jira)
3. Update the Feature on JA and wait it try to sync
4. Query the table tblRequestsAudit for this Feature and see the column _ValidTo

Expected Results

Only one entry on tblRequestsAudit would keep the _ValidTo as NULL

Actual Results

More than one entry is having the _ValidTo as NULL

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available