Options related to incomplete executions

the following options in {{product name}} {{scenario singular lowercase}} settings determine if and how the incomplete executions are stored allow storing incomplete executions this option enables incomplete executions for the {{scenario singular lowercase}} if this option is disabled, {{product name}} doesn't store incomplete executions of the {{scenario singular lowercase}} sequential processing sequential processing ensures that the {{scenario singular lowercase}} runs in a sequence if there is an incomplete execution of the {{scenario singular lowercase}} , {{product name}} pauses further scheduling of the {{scenario singular lowercase}} to keep the processing in the chronological sequence {{product name}} activates the {{scenario singular lowercase}} again after the {{scenario singular lowercase}} has no incomplete executions if the {{scenario singular lowercase}} has instant scheduling, {{product name}} stores the arriving bundles in the webhook queue enable data loss data loss setting controls what should happen when {{product name}} cannot create an incomplete execution of a failed {{scenario singular lowercase}} run this happens in most cases because the incomplete execution storage is full incomplete execution storage is limited based on the usage allowance if you keep data loss disabled, {{product name}} pauses scheduling of the {{scenario singular lowercase}} to avoid losing any more {{scenario singular lowercase}} runs, until you clear the incomplete execution storage and enable the {{scenario singular lowercase}} again if you enable data loss, {{product name}} will continue scheduling the {{scenario singular lowercase}} even if it couldn't store the incomplete execution