Thank you for the idea submission. Datafeeds are compiled across all affiliates via an overnight process. The length of the job that creates them depends on the amount of changes/data that needs to be included per affiliate per feed. Typical this job completes by business hours (7-8am CST) but can take longer if there are significant changes. Our teams are always working to fine tune these processes to make them more efficient and less time consuming, but this is where we are at right now. We have alerts that let us know if this datafeed job is failing or having issues and our teams always hop right on them to correct as soon as possible. Datafeeds can also fail on the client side if there are issues with your SFTP connection. As a reminder, datafeeds can be manually downloaded within Client Admin and also be re-sent to your SFTP from client admin, speak with your CSM if you are not sure how either of these functions work. If you set your client side imports to not run either until a file is received via SFTP or set them to run after lunch time each day (after 12pm for example), you should be able to have successful imports on a daily basis. We cannot implement SLAs to this service as the service is variable as described.

This is exactly the same issue we are facing, with some reports being delivered during the early hours Europe time, but 1 other data feed mid-afternoon, meaning we cannot provide users with a refreshed data set until at least 48hours after meaning our reporting is less dynamic than we'd wish.