Sometimes if the asset updates in widen are getting lost in sync If we choose the below options
With Transcode option and updated date as synchronization method. we are getting the assets which are modified after the last sync and before the requested time, but as we are using the transcode option to get the asset we are reducing the time frame by 1 hour for getting the widen cdn to be consistent.
So that means lets say Last sync happened at 8AM and sync interval is 2 hours with transcode option. so we are trying to get the asset which are updated after 8AM and before 9AM(as next run is at 10AM and cutoff is 1 hour) because of this we are loosing the assets for the timeframe of 9AM to 10AM because last sync is at 10AM and next sync happens at 12PM again we are trying to get the assets from 10AM to 11AM.
In a way we are always loosing the updates made in an hour.
As we are cutting the request time by 1hour we need to cut the last sync also by one hour to not to loose the asset updates.
Active
2.0
Code
Decreased the Last modified time also by 1hour in Query to not to loose the asset updates.
@mattglam, can we decrease the 1 hour timeframe to 10mins?
The last submitted patch, 2: 3380127-2-lost-asset-updates-when-using-transcode-option.patch, failed testing. View results →