Types of warnings

within a {{scenario singular lowercase}} , you can have numerous modules and item mappings together, they create your {{scenario singular lowercase}} each of these elements can create an event that might need your attention a warning a warning can also be the result of handling an error with the error handler docid\ hxe6n1fool691glswodgy with the warning {{product name}} informs you that the break error handler created an incomplete executions docid 6zznn7v35herrcjfccp9q of your {{scenario singular lowercase}} the main difference between a warning and an error is, that a warning doesn't disable the scheduling of your {{scenario singular lowercase}} and warnings don't count into the overview of error handling docid 7 hehdtuu2xyys8 qurub when a module returns a warning, {{product name}} highlights the module with the "warning" sign to check the error type, click the thought bubble above the module when you use error handling, you will see a warning when the error handler activates in the example, the error handler docid\ hxe6n1fool691glswodgy handled the types of errors docid\ n4w0yaeop7a a4vfw ebp the error handler activation turned the original error into a warning executioninterruptederror a module outputs the executioninterruptederror when the {{scenario singular lowercase}} runs for more than 40 minutes (5 minutes for the free subscription) the module that is currently processing data outputs the warning when a module outputs the executioninterruptederror the {{scenario singular lowercase}} ends with a warning the {{scenario singular lowercase}} doesn't process the remaining bundles {{product name}} will keep scheduling further {{scenario singular lowercase}} runs to fix the executioninterruptederror , consider strategies to optimize your {{scenario singular lowercase}} split your {{scenario singular lowercase}} you can use the combination of the following modules for example, if you are processing a lot of bundles in a {{scenario singular lowercase}} with 20 modules and the {{scenario singular lowercase}} ends with the executioninterruptederror , you can split the {{scenario singular lowercase}} into two {{scenario plural lowercase}} with 10 modules each set the search modules' limit to a lower number to reduce the amount of data processed by the {{scenario singular lowercase}} check the api documentation of the apps you use in the {{scenario singular lowercase}} if the app’s api has a suitable endpoint that supports batch requests, you can use the json aggregator and the http app to send your data in batches in addition, you save on operation usage outofspaceerror data store modules output the outofspaceerror when {{product name}} cannot store any more data in the data store you also get the outofspaceerror when you fill your incomplete execution storage if a module outputs the outofspaceerror with no error handling, the {{scenario singular lowercase}} ends with a warning the {{scenario singular lowercase}} doesn't process the remaining bundles {{product name}} will keep scheduling further {{scenario singular lowercase}} runs to fix the outofspaceerror in a {{scenario singular lowercase}} , you can use a backup data store with the error handler docid\ wr8aaeme2ptfar38vxd3p you should also check the data in the data store or your incomplete execution storage you can also review the {{product name}} pricing https //www make com/en/pricing