Export Sets have no data cleanup for attachments saved to MID Server, eventually causing performance problems for the MID ServerDescriptionExports sets save attachments to the agent\export\<Export Target File Path> folders within the MID Server installation folder. There is no cleanup implemented for these records, which will grow in number and size until the MID Server suffers performance impact. One symptom is a delayed startup check for file permissions, leaving the MID Server in Down state and unusable while that runs. Features such as SOAP/REST Integrations or Import set loads could timeout and fail during that time:e.g.06/17/21 19:57:29 (619) StartupSequencer Verifying read access to every directory and file in tree D:\...\agent06/17/21 20:19:23 (551) StartupSequencer .....= 22 minutes, for ~200k files in export\Steps to Reproduce Run an export set. Actual behaviour:The attachment will remain within the MID Server install folder for ever. The eventual build up will cause performance issues for the MID Server. Expected behaviour:Some sort of maximum retention time, limit on total number/size of files, and automatic cleanup should be part of this feature. Do this 200k times, and you will delay the startup/restart/upgrade of the MID Server by >20 minutes, as the necessary file permissions checks run (which is a security requirement). e.g. >40 minute delay has been seen on startup: 03/19/21 01:48:48 (873) StartupSequencer Verifying read access to every directory and file in tree /service-now/midserver/agent03/19/21 02:31:06 (172) StartupSequencer Getting instance ACLs for table: ecc_agent WorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available. A regular manual cleanup of the agent/export folders will be required as a workaround to prevent problems.Related Problem: PRB1507153