Download for macOS today, or join the waitlist for Windows and Linux.
Workflows / Telecommunications

Bulk Outage Processing

Processes a batch of active outage events concurrently using a Map state with a maximum concurrency of 3. Each outage is independently validated, root-cause diagnosed, and impact-assessed before field dispatch and rerouting are initiated.

Clone

GitHub icon View on Github 
{
  "Comment": "Bulk outage processing — diagnose and assess multiple simultaneous outages using Map state",
  "StartAt": "ProcessOutageBatch",
  "States": {
    "ProcessOutageBatch": {
      "Type": "Map",
      "ItemsPath": "$.outages",
      "MaxConcurrency": 3,
      "ItemProcessor": {
        "ProcessorConfig": {
          "Mode": "INLINE"
        },
        "StartAt": "ValidateReport",
        "States": {
          "ValidateReport": {
            "Type": "Task",
            "Resource": "arn:aws:states:::lambda:invoke",
            "Parameters": {
              "FunctionName": "${ValidateOutageReportFunctionArn}",
              "Payload.$": "$"
            },
            "ResultPath": "$.validation",
            "Retry": [
              {
                "ErrorEquals": [
                  "Lambda.ServiceException",
                  "Lambda.AWSLambdaException",
                  "Lambda.SdkClientException",
                  "Lambda.TooManyRequestsException"
                ],
                "IntervalSeconds": 2,
                "MaxAttempts": 3,
                "BackoffRate": 2
              }
            ],
            "Next": "InvestigateInParallel"
          },
          "InvestigateInParallel": {
            "Type": "Parallel",
            "Branches": [
              {
                "StartAt": "DiagnoseRootCause",
                "States": {
                  "DiagnoseRootCause": {
                    "Type": "Task",
                    "Resource": "arn:aws:states:::lambda:invoke",
                    "Parameters": {
                      "FunctionName": "${DiagnoseRootCauseFunctionArn}",
                      "Payload.$": "$.validation.Payload"
                    },
                    "End": true
                  }
                }
              },
              {
                "StartAt": "AssessImpact",
                "States": {
                  "AssessImpact": {
                    "Type": "Task",
                    "Resource": "arn:aws:states:::lambda:invoke",
                    "Parameters": {
                      "FunctionName": "${AssessImpactRadiusFunctionArn}",
                      "Payload.$": "$.validation.Payload"
                    },
                    "End": true
                  }
                }
              }
            ],
            "ResultPath": "$.investigation",
            "Next": "GenerateReport"
          },
          "GenerateReport": {
            "Type": "Task",
            "Resource": "arn:aws:states:::lambda:invoke",
            "Parameters": {
              "FunctionName": "${GenerateIncidentReportFunctionArn}",
              "Payload.$": "$.investigation[1].Payload"
            },
            "ResultPath": "$.report",
            "Retry": [
              {
                "ErrorEquals": [
                  "Lambda.ServiceException",
                  "Lambda.AWSLambdaException",
                  "Lambda.SdkClientException",
                  "Lambda.TooManyRequestsException"
                ],
                "IntervalSeconds": 2,
                "MaxAttempts": 3,
                "BackoffRate": 2
              }
            ],
            "End": true
          }
        }
      },
      "ResultPath": "$.processedOutages",
      "Next": "BulkOutageComplete"
    },
    "BulkOutageComplete": {
      "Type": "Succeed"
    }
  }
}
JSON
Expand
100%

Telecommunications teams can use patterns like this to build reliable, compliant, and scalable automation for payment systems and can test and refine these flows locally with Thrubit to reduce cloud cost and speed up iteration.

Related Workflows

More Telecommunications Workflows from Network Outage Management

Outage Management Pipeline

Telecommunications
End-to-end network outage management pipeline. Validates the outage report, diagnoses the root cause across affected network segments, assesses the impact radius and number of affected subscribers, dispatches field technicians, applies network rerouting to restore partial service, executes full service restoration, and generates the incident report for SLA tracking.

Outage Escalation

Telecommunications
Escalation workflow for unresolved or recurring network outages. Re-validates the outage report, enforces a Wait state for network stabilization, runs parallel root-cause re-diagnosis and impact re-assessment in a Parallel state, then re-dispatches field resources or escalates to network operations leadership with a structured SLA breach report.

Express Outage Triage

Telecommunications
Express triage workflow for immediate outage severity classification. Validates the incoming outage report and immediately diagnoses the root cause to return a real-time severity and affected-subscriber count, enabling NOC teams to prioritize dispatch and rerouting actions without waiting for the full pipeline.