Scoutflo Documentation
  • 🚀Welcome to Scoutflo💙
  • Overview
    • What is Scoutflo?
    • Getting Started
    • Scoutflo Architecture
    • Basic Concepts
    • Our Products
  • Our Products
    • Scoutflo Deploy
    • Scoutflo Atlas
      • About
      • Key Features
      • Scoutflo Sandbox
        • How to use
        • Available Product Sandboxes
      • Scoutflo Health Score
        • Overview
        • Key Metrics
          • Security Key Elements
          • Code Quality & Maintenance Key Elements
          • Support Key Elements
          • Community Activeness Key Elements
          • Business Readiness Key Elements
        • Calculation
        • Use case of these Scores
        • Process of Score calculation
        • FAQ
      • Product Qualification
      • Find the right product
      • Product Information and Maintenance
      • Product Stakeholders
  • Key Feature
    • Infrastructure Provisioning
      • Create a new Cluster
        • Add Credentials
        • VPC Configuration
      • Edit an existing Cluster
        • Security Scans for Cluster
      • Delete a Cluster
    • Service Deployment
      • Service Onboarding
      • Service Cost Prediction
      • Service Deployment
      • Delete a Service
    • Helm Service Deployment
      • Customized Helm Deployment
      • Open Source Helm Deployment
      • Open Source Service Catalog
      • Edit an App
      • Delete an App
    • Database Deployment
    • RBAC
      • Set Up your custom Roles
    • Workspace
    • Dora Dashboard
    • Kubernetes Dashboard
    • Notification (Coming Soon)
    • Alert Management
      • Default Alert Rules
  • Guide
    • Terraform and Scoutflo
    • AWS EKS Best Practices Guide
    • Kubernetes and Scoutflo
    • ArgoCD and Scoutflo
    • Connect your Cloud
    • Scoutflo Deploy Free Trial Cluster
    • Add-on deployments
    • Custom Configurations
    • Terminology Guide
    • Workflow Action ID
  • Integrations
    • Scoutflo Integration
    • Version Control tool
      • GitHub App
    • Container Registry
      • AWS ECR Container Registry
      • Docker Hub Container Registry
    • Slack
    • Scoutflo Add-Ons
  • Fundamentals
    • GitOps with Scoutflo
    • Container/OCI Registry
    • Monitoring
    • AWS EKS Cluster
    • List of IAM permissions for your scoutflo IAM user on AWS
  • FAQs
    • General
    • Scoutflo Atlas
    • Scoutflo Deploy
    • Scoutflo Sandbox
    • Contact Us
  • Glossary
Powered by GitBook
On this page
  • Workflow Action ID
  • How to Use the Workflow Action ID
  • Raising a Support Ticket with Workflow Action ID
  1. Guide

Workflow Action ID

In our platform, we support several key actions that users can perform on resources, including:

  1. App Deployment

  2. App Deletion

  3. Cluster Deployment

  4. Cluster Deletion

Each of these actions requires a set of tasks to be executed in a specific sequence. To manage these actions, our platform organizes all related tasks into what we call a workflow. Each workflow is assigned a unique Workflow Action ID to ensure easy tracking, auditing, and troubleshooting.

Workflow Action ID

The Workflow Action ID is a unique identifier assigned to each action (such as deploying or deleting an app or cluster) performed on the platform. It serves as a reference point for all activities related to that specific action, capturing essential details such as task metadata, execution logs, and user information. This ID enables both you and our support team to quickly access the complete history and status of each action for troubleshooting and auditing.

Structure of the Workflow Action ID

Each Workflow Action ID is constructed by combining:

  1. Type of Action – This specifies the action type (e.g., app_deploy, app_delete, cluster_deploy, cluster_delete).

  2. Unique UUID – A universally unique identifier that ensures each Workflow Action ID is distinct.

Example: For an app deployment, the Workflow Action ID might look like:

app_deploy-123e4567-e89b-12d3-a456-426614174000

Information Captured in the Workflow Action ID

Each Workflow Action ID is linked to detailed records that include:

  1. Task Metadata – Information on each task within the workflow, including task type, status, start and end times, dependencies, and any error codes.

  2. User Metadata – Information about the user who initiated the workflow (e.g., user ID, role, and organization).

  3. Task Logs – Logs capturing the output and status of each task, providing insights into the workflow's progress and any issues encountered.

  4. Timelines and Debugging Details – Time-stamped entries showing the start and completion of each task, along with any additional debugging information.

These details provide complete visibility into each action performed on the platform, ensuring traceability and accountability.

How to Use the Workflow Action ID

The Workflow Action ID can be used for:

  1. Auditing and Compliance – Reviewing past actions and ensuring accountability for each operation.

  2. Troubleshooting – If an action encounters an error, the Workflow Action ID provides a way to access the entire history of tasks within that workflow for debugging.

  3. Support Requests – The Workflow Action ID is essential for quickly resolving any issues you may encounter on the platform.

Raising a Support Ticket with Workflow Action ID

If you encounter any issues or if an action fails, please follow these steps to raise a support ticket:

  1. Copy the Workflow Action ID – Every action you perform will generate a Workflow Action ID upon initiation. You can find this ID in the task logs or action history for reference.

  2. Submit a Support Ticket – When submitting your support request, include the Workflow Action ID. This ID allows our support team to access all related logs, user information, and execution details, streamlining the troubleshooting process.

  3. Receive Updates and Solutions – Our support team will investigate the issue using the Workflow Action ID. Since this ID provides all the necessary information, our team can analyze the task sequence, pinpoint any errors, and update you promptly with the solution or next steps.

By using the Workflow Action ID when reaching out for support, you help us ensure quick and effective resolution of any issues you may face on the platform.


Note: Use the Workflow Action ID as your primary reference for all actions on the platform. It is essential for tracking progress or raising support tickets, ensuring full visibility and

PreviousTerminology GuideNextScoutflo Integration

Last updated 7 months ago