Skip to content
Scope4mation · Service Automation Suite
SASService Automation Suite
SAS Wiki
AvailablePublicDoc version 1.0Source reviewed 2026-08-22

Ausführungsverhalten & Wiederherstellung

Understand what remains after failures and aborts.

On this page
Übersetzung in Arbeit

Navigation und Seitenzusammenfassung sind auf Deutsch. Der technische Inhalt dieser Seite ist vorläufig noch auf Englisch und wird schrittweise übersetzt.

API Composer

  • Only one run per sequence or stand-alone request can be active at a time.
  • A Fatal failure skips the remaining requests; a Functional failure allows the sequence to continue.
  • Aborting does not undo rows already written.
  • With polling enabled, output is written only when the Continue rule matches.
  • A rate-limit response is retried automatically according to the documented limits.
  • Truncate and Insert clears the target data set at the start of the run and has no undo.

Dataflow Composer

  • Only one import per dataflow runs at a time.
  • The existing output remains available until a new import succeeds completely.
  • A failed or aborted import leaves the previous output unchanged.
  • Every successful import replaces the complete output data set.

Endpoint Composer

When a write call contains several records, successful records remain written even when other records fail. The response reports failures per record, so callers must not interpret a partly failed response as an all-or-nothing transaction.

Take the next step

Use the reference material for details or discuss your question with the team.

Ask your question