DEENESPTFRRUARHIKOZHNL

struct ara::diag::SovdBulkData::DeletionError

[SWS_DM_01844] Upstream: RS_Diag_04266

struct DeletionError {...};

Definition of DeletionError for a single bulk-data instance.

Header-Datei#include "ara/diag/sovd_bulk_data.h"
Forwarding-Header#include "ara/diag/diag_fwd.h"
Scopeclass ara::diag::SovdBulkData

User GuideAI-GENERATED

Encapsulates metadata and the error cause of an individual bulk data object whose deletion failed.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 6e6e835c2f85 Provenance Open questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

Encapsulates metadata and the error cause of an individual bulk data object whose deletion failed.

The structure [SWS_DM_01844] represents the error result of a failed deletion operation of an individual bulk data object in the SOVD diagnostic module (AUTOSAR_AP_SWS_Diagnostics §8.53.4 “Struct: DeletionError”). It links the metadata of the undeleted data element item with the occurred error code error [SWS_DM_01845], [SWS_DM_01846]. As a pure value object, it serves the caller for targeted identification and root-cause analysis of failed cleanups.

Context

The data structure [SWS_DM_01844] describes an individual error that occurs during the deletion process of bulk data within the SOVD framework (Service-Oriented Vehicle Diagnostics) of AUTOSAR Adaptive (AUTOSAR_AP_SWS_Diagnostics §8.53.4 “Struct: DeletionError”). As part of the interface ara::diag::SovdBulkData, the structure serves to establish a precise association between the affected data element and the error cause during failed cleanup or deletion actions. In doing so, it connects the metadata descriptor of the non-deletable file with a standardized AUTOSAR error code.

Interaction occurs primarily between the diagnostic server or the component ara::diag::SovdBulkData that executes the deletion and the calling diagnostic or application logic. The latter requests the cleanup of bulk data and, in the event of an error, receives feedback to determine which specific data records could not be removed and why. The interaction of the involved components and the return of the error object during a deletion attempt are shown in the following sequence diagram.

Error handling sequence during bulk data deletionClientSovdBulkDataRequest deletion job for bulk dataDeletion attempt for data item failsReturn DeletionError (item, error)Evaluation of item and error (ara::core::ErrorCode)

Sequence diagram: Typical sequence of a failed bulk data deletion with return of DeletionError. Sources: [SWS_DM_01844], [SWS_DM_01845], [SWS_DM_01846], AUTOSAR_AP_SWS_Diagnostics §8.53.4.1 “Public Member Variables”

Lifecycle

The structure [SWS_DM_01844] is designed as a pure value object (Plain Old Data / value type). Its instantiation takes place on the diagnostic infrastructure side precisely when an error is detected during the processing of a deletion job for a specific bulk data element. In doing so, the field item is initialized with the corresponding BulkDataMetaDataDescriptor [SWS_DM_01845] and the field error with the specific error code ara::core::ErrorCode [SWS_DM_01846].

Regarding ownership, the instance (or a collection of such instances) typically transitions into the ownership of the caller as a return value or within an error container. Interpretation: The structure has no long-lived resources or active threads of its own; its lifecycle is directly tied to the scope of the calling error handling block or result container. Question Q-60f135b9e36d7083 (open) After evaluation by the application, the structure together with its member variables is destroyed by default on the stack or in the heap. Since it is a passive data packet, no internal state transitions or concurrent synchronization requirements occur within the structure.

Usage Path

In the regular use case, a diagnostic component or an SOVD client initiates the deletion of one or more bulk data objects via the interface SovdBulkData. If the deletion of at least one element fails, the platform creates an instance of DeletionError [SWS_DM_01844].

The caller receives the error object and evaluates the two public variables (AUTOSAR_AP_SWS_Diagnostics §8.53.4.1 “Public Member Variables”):

  • item: Via the BulkDataMetaDataDescriptor, the application identifies the concrete data element whose deletion failed [SWS_DM_01845].
  • error: Based on the ara::core::ErrorCode, the application determines the exact cause for the failure of the deletion process [SWS_DM_01846].

Based on this information, the calling logic can react in a differentiated manner, for example by logging the error, choosing an alternative cleanup strategy, or reporting the detailed error cause to a higher-level SOVD client.

Error Scenarios

The structure DeletionError does not throw exceptions itself and does not report its own error codes, but serves exclusively as an information carrier for encapsulating failures of preceding deletion operations. The central error semantics are provided via the variable error of type ara::core::ErrorCode [SWS_DM_01846]. This code specifies in detail why the bulk data object [SWS_DM_01845] referenced by item could not be deleted (for example, access denial, locked resources, or file system errors).

As a precondition for meaningful evaluation, the variables item and error must have been populated with valid context data by the creating SovdBulkData runtime environment. After completion of the inspection, the structure requires no cleanup actions by the developer.

This guide is based exclusively on the specification excerpts of AUTOSAR Adaptive R25-11.

UML class diagram

Hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); Klicken öffnet die jeweilige Klassenseite.

G nara__diag__SovdBulkData__DeletionError56 «struct» DeletionError + error + item

Constants

error variable

Corresponding error, that specifies why the bulk data could not be deleted.

item variable

bulk data that could not be deleted.

Documentation of constants / variables

variable error [SWS_DM_01846] Upstream: RS_Diag_04266

ara::core::ErrorCode error;

Corresponding error, that specifies why the bulk data could not be deleted.

Header-Datei#include "ara/diag/sovd_bulk_data.h"
Scopestruct ara::diag::SovdBulkData::DeletionError
Symbolerror
Typara::core::ErrorCode

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01846
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01846@rel:R25-11#6ff3444c
Content hash
6ff3444c
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01846
Status: valid/unmigrated Version: rel:R25-11#5fc21fda Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01846@rel:R25-11#5fc21fda
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#6ff3444c2026-09-30
  • R23-11rel:R23-11#bbba0cd42026-10-14
  • R24-11rel:R24-11#bbba0cd42026-10-14
  • R25-11rel:R25-11#5fc21fda2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variable item [SWS_DM_01845] Upstream: RS_Diag_04266

BulkDataMetaDataDescriptor item;

bulk data that could not be deleted.

Header-Datei#include "ara/diag/sovd_bulk_data.h"
Scopestruct ara::diag::SovdBulkData::DeletionError
Symbolitem
TypBulkDataMetaDataDescriptor

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01845
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01845@rel:R25-11#81ffea3c
Content hash
81ffea3c
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01845
Status: valid/unmigrated Version: rel:R25-11#656f0547 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01845@rel:R25-11#656f0547
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#81ffea3c2026-09-30
  • R23-11rel:R23-11#2453664f2026-10-14
  • R24-11rel:R24-11#2453664f2026-10-14
  • R25-11rel:R25-11#656f05472026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill