Skip to content
Scope4mation · Service Automation Suite
SASService Automation Suite
SAS Wiki
AvailablePublicSource reviewed 2026-08-22

Límites de un vistazo

Important limits and irreversible behaviors across documented components.

On this page
Traducción en curso

La navegación y el resumen de la página están en español. El contenido técnico de esta página permanece temporalmente en inglés y se traducirá de forma gradual.

API Composer

  • Folders can be nested up to three levels.
  • Only one run per sequence or stand-alone request can be active at a time.
  • Truncate and Insert clears the target data set at the start of the run and cannot be undone.
  • Changing a request address clears the discovered response structure.
  • Discovery performs a real API call.
  • A Fatal failure skips the remainder of a sequence.
  • The dedicated Logging section has no content yet.

Dataflow Composer

  • Folders can be nested up to three levels and must be empty before deletion.
  • Every successful import replaces the complete output data set.
  • The previous output remains intact until a new import succeeds fully.
  • Only one import per dataflow can run at a time.
  • Aggregate results cannot feed functoids or other aggregates directly.
  • A dataflow cannot use itself as a source.

Endpoint Composer

  • API keys are shown once and can expire no more than one year after creation.
  • Endpoint names are unique across the entire instance.
  • Renaming an endpoint changes its runtime address.
  • A read returns at most 500 rows per call and requires the caller to supply a limit.
  • Endpoint Composer has no run history, call log, or usage overview.
  • Deleting a folder can leave its endpoints published but no longer visible in the tree.

Open the component administration page before performing destructive or security-sensitive changes.

Take the next step

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

Ask your question