Skip to content
Proud to collaborate with Microsoft for Startups

network.enqueue-scope-syncs ​

Fan out network scope sync workflows

Start scope sync workflows for all discovered scopes in one account.

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-network
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
network_account_uuiduuidYes——
organization_uuiduuidYes——
workflow_run_uuidstringNo—Engine-stamped parent run UUID (DAG step target)
workflow_run_idstringNo—Engine-stamped DAG run ID (injected when used as a DAG step)
wait_for_childrenbooleanNo—When true, wait for child scope sync terminal states

Output Schema ​

FieldTypeRequiredDefaultDescription
network_account_uuiduuidYes——
organization_uuiduuidYes——
workflow_run_uuidstringNo——
workflow_run_idstringNo—Engine-stamped DAG run ID (injected when used as a DAG step)
wait_for_childrenbooleanNo——
fanout_started_atstringYes——
network_scope_sync_workflow_uuidsjsonYes——
pending_scope_sync_workflow_uuidsjsonYes——
completed_scope_sync_workflow_uuidsjsonYes——
failed_scope_sync_workflow_uuidsjsonYes——
started_scope_sync_countintegerYes——
skipped_scope_sync_countintegerYes——
completed_scope_sync_countintegerYes——
failed_scope_sync_countintegerYes——
completed_atstringNo——
failed_atstringNo——
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
initiatedYesNo—fanout—
fanoutNoNo———
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedfanoutfanout—
fanoutchild_donefanout—
fanoutchild_failedfanout—
fanoutcompletecompleted—
fanoutfail_childrenfailed—
* (any state)failfailed—

Outcomes ​

OutcomeTypeDescriptionState Data Keys
enqueuedSUCCESSFan out network scope sync workflows—
failedFAILURENetwork workflow failedfailure_reason

API Usage ​

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

{
  "workflow_type": "network.enqueue-scope-syncs",
  "initial_data": {
    "network_account_uuid": "value",
    "organization_uuid": "value"
  }
}