To maintain stability, we do need to enforce an expiration date to ensure exports that are automatically generated are being utilized by users. Scheduled exports are notorious for users to stop using them and never bother to stop the export run. Years ago we ran without a limit and we ended up in a situation where the bulk of scheduled exports being run every hour were not even being downloaded. (At that time emailing the report was not an option.) Enforcing a limit reduced traffic by more than 75%.
Of course we do want to find a happy medium to enforce a limit and ensure users critical exports are not turned off unexpectedly. A few features and upcoming features we have that addresses this:
- Expired exports can be re-enabled. There should never be a situation where you need to completely rebuild and reschedule an export because it expired.
- Within the schedule exports screen, the user can confirm the schedule ahead of the expiration period to reset the 100 day timer.
- We're building notification tools into the UI. The inbox section where exports can be downloaded will show a count of exports expiring soon and exports that have expired. It will have the ability to refresh all expiring exports with a single click. A daily summation email will be delivered to note exports that have expired and are expiring soon.
------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------