Fix missing data errors

app modules output the bundlevalidationerror when the input bundle is missing the required data for example, if you map data from a search module that didn't return any results when a module in your outputs the bundlevalidationerror , you should check the reason for the error you should consider redesigning your if you can avoid the error to make your automation more robust you can use the if docid\ pmt2j3ndx4b4bp51gxk6t or ifempty docid\ pmt2j3ndx4b4bp51gxk6t functions or use filtering docid\ toeivu0dbv44bmrjcmlic otherwise, you will have to handle the error to keep your active in the following examples, we will consider two situations ignore the missing data or use a placeholder the missing data are not a problem you just want to keep your enabled get notified about errors and store the run the missing data are not acceptable if you get the bundlevalidationerror , you want to check what happened in detail to learn more about how to approach error handling in you can check the overview of error handling docid\ sn7mce4qml q6wdtoocsy ignore the missing data or use a placeholder you might work with data that sometimes contains missing values you don't need to fix them or investigate why they are missing your main goal is to avoid disabling your we will use the following for testing the reads data, modifies it, and uses it for a search in the data store one piece of data is empty, which causes the bundlevalidationerror in the search module to keep your running even when the error happens, you can use the skip error handler docid\ j9xcttcbfdwq3q3u144fn or resume error handler docid 7xrugbey0utl58ucpwp7v right click the module that is causing the error select add an error handler a pop up appears from the list of error handlers, select the skip error handler the final should look like this ignore error handler in the above image has been renamed to skip get notified about errors and store the make run there might be you want to check closely when an error happens you can do that with a custom error handling setup if an error occurs in your , you get an email with the error description and a link to the in addition, you store the error bundle as incomplete execution to resolve it manually we will use the following for testing the reads data, modifies them and uses them for search in the data store one piece of data is empty, which causes the bundlevalidationerror in the search module to store unfinished runs and get a custom email notification when an error occurs, follow these steps right click the module that is causing the error select add an error handler a pop up appears from the list of error handlers, select the retry error handler a pop up appears with the retry error handler settings set automatic completion to no to always resolve the error manually confirm the settings with the ok button to learn more about the retry error handler settings, see the retry error handler docid\ cptwi8yi45zl3m5slzjnv topic click the settings icon and enable storing of incomplete executions right click the connection between the erroring module and the retry error handler choose add a module make inserts a gray module placeholder between the erroring module and the retry error handler click the gray module placeholder and search for the gmail app insert the send an email module into the module placeholder set up the send an email module in the content field, add the notification message you want to receive when an error happens use the system variables docid 5uj3 0kgud4jwffmxam 9 to get the metadata for example you set up error handling in your to create an incomplete execution and notify you with an email when an error happens the example with error handling looks like this break error handler in the above image has been renamed to retry