SNIP_ADAPTIVE_PLATFORM_FIGURE_Figure_7_11_STATEMANAGEMENT

Figure 7.11: ErrorRecoveryTable T o ensure that all errors are covered the following constraint is needed: [SWS_SM_CONSTR_00014] Handling of non-mapped ExecutionError ⌈Each ErrorRecoveryTable shall have exactly one entry configured with value ANY as the ExecutionError⌋ The ANY entry will be used to change to the configured StateMachine State when a not configured ExecutionError is reported by Platform Health Management or Execution Management . During an active update session, handling of the recovery actions (see [SWS_SM_00601] and [SWS_SM_00664]) should be treated differently , depending on whether the StateMachine itself is "ImpactedByUpdate" [SWS_SM_00654] or not. Otherwise errors occurred during or after methods called by the Update and Configuration Management could result in StateMachines transiting to recovery StateMachine State , which might not be the intended action. [SWS_SM_00601] StateMachine error notification reaction of StateMachines not "ImpactedByUpdate" Upstream requirements: RS_SM_00001, RS_SM_00005 ⌈When EventexecutionErrorEvent::ExecutionError is reported from Platform Health Management or from Execution Management and the StateMachine is not "ImpactedByUpdate", StateMachine shall • set internal flag that error recovery is ongoing • evaluate the next StateMachine State configured for executionError from ErrorRecoveryTable • stop processing ActionListItems from the ActionList referencing the current StateMachine State • switch to the next StateMachine State immediately and start processing ActionListItems from the ActionList referencing this StateMachine State ⌋