Export set "Scheduled Data Exports" intermittent 'Completed with errors' Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Export set "Scheduled Data Exports" intermittent failed and in the 'sys_export_set_run' table, it will show some with status 'Completed with errors' and "error "'Bytes Transferred' value for MID Server Attachment sys_id : xxxx is invalid" Usually happens after change/move to another MID server. CauseThis behavior might be caused by some kind of network connectivity/congestion issue.ResolutionTry the following steps below to see where the issue lies: Run this export set during non-peak hours (no discovery job or other integration is running) to rule out any network congestion. If still persist the same, go to step Recycle the MID server and validate that the above error goes away. If the issue still persists, try step 3.Run this schedule on a separate Install MID server (Note: You will need to change the export sets location to use the new mid server)Set System Properties -> Import Export -> Export Set -> MID Server Response Timeout -> Current Value from the default of 300 to a higher value, e.g. 900