Fixing 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 {{scenario singular lowercase}} outputs the bundlevalidationerror , you should check the reason for the error you should consider redesigning your {{scenario singular lowercase}} if you can avoid the error to make your automation more robust you can use the general functions docid\ pmt2j3ndx4b4bp51gxk6t or general functions docid\ pmt2j3ndx4b4bp51gxk6t functions or use filtering docid\ toeivu0dbv44bmrjcmlic otherwise, you will have to handle the error to keep your {{scenario singular lowercase}} 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 {{scenario singular lowercase}} enabled get notified about errors and store the {{scenario singular lowercase}} 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 {{product name}} you can check the overview of error handling docid 7 hehdtuu2xyys8 qurub ignore the missing data or use a placeholder you might work with data that sometimes contain missing values you don't need to fix them or investigate why they are missing your main goal is to avoid disabling your {{scenario singular lowercase}} we will use the following {{scenario singular lowercase}} for testing the {{scenario singular lowercase}} 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 keep your {{scenario singular lowercase}} running even when the error happens, you can use the ignore error handler docid\ xzfc2uhei4kmsmhydbnmp or resume error handler docid\ wr8aaeme2ptfar38vxd3p error handlers 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 ignore error handler the final {{scenario singular lowercase}} should look like this get notified about errors and store the make run there might be {{scenario plural lowercase}} 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 {{scenario singular lowercase}} , you get an email with the error description and a link to the {{scenario singular lowercase}} in addition, you store the error bundle as incomplete execution to resolve it manually we will use the following {{scenario singular lowercase}} for testing the {{scenario singular lowercase}} 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 {{scenario singular lowercase}} 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 break error handler a pop up appears with the break 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 break error handler settings, check the break error handler docid\ hxe6n1fool691glswodgy click the {{scenario singular lowercase}} settings icon and enable storing of incomplete executions right click the connection between the erroring module and the break error handler choose add a module make inserts a gray module placeholder between the erroring module and the break 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 {{product name}} variables docid 5uj3 0kgud4jwffmxam 9 to get the metadata for example you set up error handling in your {{scenario singular lowercase}} to create an incomplete execution and notify you with an email when an error happens the example {{scenario singular lowercase}} with error handling looks like this