Skip to content
Proud to collaborate with Microsoft for Startups

data.network.segment.persist ​

Upsert a NetworkSegment from sync

Create, restore, or update a NetworkSegment by (scope, provider_segment_ref).

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-network
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—UUID of the organization
network_scope_uuiduuidYes—UUID of the parent NetworkScope
provider_segment_refstringYes—Provider-side segment identifier (subnet-..., subnetId, etc.)
namestringYes—Human-readable segment name
cidr_blockslistNo—CIDR blocks for the segment
availability_zonestringNo—AZ / zone where the segment lives
route_domainstringNo—Route table or domain identifier
classificationstringNo—public/private/hybrid classification
is_publicbooleanNo—Whether the segment is provider-public
provider_metadatadictNo—Provider-side metadata bag (no secrets)
actorstringNo—Caller initiating the persist

Output Schema ​

FieldTypeRequiredDefaultDescription
segment_uuiduuidYes—UUID of the persisted segment
createdbooleanYes—True when a new row was inserted
restoredbooleanYes—True when a soft-deleted row was restored
updatedbooleanYes—True when an existing row was mutated
persisted_atstringYes—ISO-8601 timestamp of the persist
failure_reasonstringNo—Engine-stamped human-readable failure reason
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped step name (DAG path)
failed_layerintegerNo—Engine-stamped layer index (DAG path)
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—completePersist segment
completedNoYesYes—Persisted
failedNoYesNo—Persist failed

State Diagram ​

Transitions ​

FromActionToDescription
pendingcompletecompleted—
pendingfailfailed—

Outcomes ​

OutcomeTypeDescriptionState Data Keys
persistedSUCCESSUpsert a NetworkSegment from sync—
failedFAILURENetwork workflow failedfailure_reason

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "data.network.segment.persist",
  "initial_data": {
    "organization_uuid": "value",
    "network_scope_uuid": "value",
    "provider_segment_ref": "value",
    "name": "value"
  }
}