Documentation
What's NewUKG.comMarketplaceUKG Pro status

Packaging and Scale Guidance

Understanding Compose Base, Premium, and add-ons to choose the right SKU for your workload.

Packaging and Scale Guidance

Note: Compose is only available for Beta testing. See Welcome to UKG Compose > Beta Disclosure for more information.

This page helps you understand UKG Compose packaging options and choose the right SKU based on your workflow workload characteristics. Use this guidance when planning your Compose deployment, troubleshooting capacity limits, or evaluating when to upgrade from Base to Premium.

Understanding UKG Compose SKUs

UKG Compose offers two primary SKUs and two add-ons:

  • Compose Base - Starting point for workflow automation
  • Compose Premium - Higher-capacity option for larger workflow footprints and high-concurrency scenarios
  • Workflows Add-on - Adds active workflow capacity and storage (available for both Base and Premium)
  • Concurrent Executions Add-on - Adds concurrent execution capacity (Premium only)

Your specific entitlements (number of workflows, concurrent executions, storage capacity) are defined in your license agreement. This page focuses on helping you understand what those limits mean and when to consider different SKU options.

Key Capacity Concepts

Active Workflows

What is a Workflow?

A Workflow is how Compose turns policies into action. It bundles logic, integrations, and human-in-the-loop steps to automate processes. Forms, Chats, and Webhooks (APIs) are all implemented as Workflows under the hood.

When does a Workflow count as Active?

A Workflow counts as Active on a given day if:

  1. It is published (not in draft mode).
  2. It has at least one production execution that day.

Simple litmus test: If you published a workflow and it ran executions, it's active.

Important notes:

  • Manual test runs and workflows that are immediately stopped don't count toward your active workflow limit
  • Draft workflows don't count as active
  • A workflow only counts as active on days when it actually runs
  • Your total active workflows = all published workflows that executed in production on a given day

When you might reach your active workflow limit:

  • You've built a large portfolio of workflows across multiple teams
  • Many scheduled workflows run daily
  • Event-driven workflows trigger frequently throughout the day
  • Multiple departments are publishing workflows for different business processes

Concurrent Executions

What is Concurrency?

Concurrency is how much work can run at once. It measures how many workflow executions can be running simultaneously.

Why concurrency matters:

Concurrency becomes critical for specific workflow patterns. Understanding which patterns consume more concurrency helps you plan capacity and choose the right SKU.

High-Concurrency Workflow Patterns

1. Approval workflows (Wait and Resume pattern)

Workflows pause while waiting for a manager or employee to approve/reject. Each paused workflow consumes a concurrent execution slot until someone responds.

Examples:

  • HCM: manager approval for compensation changes
  • WFM: timecard approval, exception review
  • Recruiting: approval gates, candidate scheduling waits
  • Talk: waiting on agent response

Why this consumes concurrency: If you have 50 approval workflows waiting for manager responses, those 50 executions are consuming concurrency even though they're not actively processing. When the 51st workflow tries to start, it may queue or fail if you've reached your concurrent execution limit.

2. Event bursts (High-volume simultaneous triggers)

Many workflows trigger at the same time, creating a spike in concurrent executions.

Examples:

  • WFM: punch burst at shift start (hundreds of employees clocking in simultaneously)
  • HCM: benefit enrollment updates processed during open enrollment periods
  • HCM: onboarding waves (many new hires starting the same day)
  • Payroll: end-of-period processing (timesheet submissions, payroll adjustments)
  • Talk/HRSD: case creation spikes triggering multi-step enrichment workflows

Why this consumes concurrency: When 200 employees punch in within the same 5-minute window, you need enough concurrent execution capacity to handle all 200 workflows running at once.

3. Scheduled batch processing (Predictable spikes)

Periodic automation that creates predictable concurrency spikes during execution windows.

Examples:

  • HCM: nightly sync/export, payroll adjustment reports
  • WFM: end-of-day timecard checks, weekly schedule processing
  • Recruiting: daily candidate digest, nightly integration syncs
  • Talk: daily backlog processing
  • PeopleFabric: nightly directory sync

Why this consumes concurrency: If you have 30 scheduled workflows all set to run at 2:00 AM, they'll all attempt to execute simultaneously, creating a concurrency spike.

4. Long-running workflows (Extended execution time)

Workflows that take minutes or hours to complete due to multi-step processes, external API calls with delays, or scheduled wait periods.

Examples:

  • Multi-step provisioning workflows with external system calls
  • Workflows with rate-limited API calls
  • Workflows with intentional delays or retry logic
  • Complex orchestration across multiple systems

Why this consumes concurrency: A workflow that takes 10 minutes to complete consumes a concurrent execution slot for those full 10 minutes, reducing available capacity for other workflows.

5. Async processing patterns (Accept fast, process later)

Workflows that accept webhook requests quickly but perform heavy processing in the background.

Examples:

  • WFM: Accept punch events fast, process policy checks asynchronously
  • HCM: Accept event quickly, perform downstream enrichment and notifications
  • Background check processing, offer generation pipelines

Why this consumes concurrency: While the webhook responds quickly, the background processing consumes concurrent execution capacity until the workflow completes.

Low-Concurrency Workflow Patterns

These patterns typically don't strain concurrency limits:

  • Scheduled workflows that complete quickly (seconds or minutes, no wait states)
  • Workflows with no approval steps or external waits
  • Workflows that run at staggered times (no overlap)
  • Simple notification or data transformation workflows
  • Workflows with low execution frequency

Data Storage

What counts toward Data Storage?

Storage in Data Tables are for high-value structured data that makes policies auditable:

  • Custom HR & WFM data used in workflow logic
  • Lookup tables and reference data
  • Decision tables and policy rules
  • Compliance records and audit trails

When you might reach storage limits:

  • Large decision tables or lookup data
  • High-volume workflows generating extensive audit logs
  • Custom data tables for business rules
  • Workflows that store binary data (documents, images, attachments)

Compose Base

What Compose Base provides:

  • Active workflow capacity for getting started or focused automation
  • Concurrent execution capacity for moderate workload patterns
  • Data storage for typical automation scenarios
  • Non-production environment included for testing and development

Best fit for:

  • Getting started with workflow automation

    • Initial adoption and learning
    • Proof of concept or pilot programs
    • Small-scale automation experiments

  • Focused use cases

    • Small number of workflows (limited to specific departments or processes)
    • Targeted business process automation
    • Single-team workflow deployment

  • Scheduled workflows with predictable cadence

    • Daily or weekly scheduled tasks
    • Workflows that complete quickly (no long wait states)
    • Low-overlap execution patterns

  • Lower concurrency needs

    • Workflows that complete quickly (seconds or minutes)
    • Limited approval workflows or wait states
    • Workflows with staggered execution times

  • Moderate data storage requirements

    • Standard execution history retention
    • Smaller decision tables and lookup data
    • Limited audit log volume

When you might outgrow Compose Base:

  • You're consistently approaching or hitting your active workflow limit
  • You're running many workflows simultaneously (high concurrency demand)
  • You have multiple approval workflows creating pending execution backlogs
  • Event-driven workflows create burst patterns that strain concurrency
  • You need larger data storage for compliance or audit purposes
  • Multiple departments want to publish workflows
  • Workflow automation is becoming central to operations, not experimental

Compose Premium

What Compose Premium provides:

  • Higher active workflow capacity (supports larger workflow portfolios)
  • Higher concurrent execution capacity (handles more simultaneous executions)
  • Higher data storage capacity (supports audit, compliance, and custom data needs)
  • Supports Concurrent Executions Add-on (not available for Base)

Best fit for:

  • Broader operational workflow footprint

    • Multiple departments publishing workflows
    • Larger portfolio of active workflows
    • Workflow automation is central to operations

  • Event-driven workflows

    • Pro HCM event triggers (job changes, terminations, new hires)
    • Webhook-triggered workflows from external systems
    • High-volume event processing

  • High-concurrency scenarios:

    Approval workflows with wait states:

    • Manager approvals for compensation changes, job changes
    • Timecard approval workflows
    • Exception review processes
    • Multi-level approval chains

    Event bursts:

    • Shift-start punch bursts (hundreds of employees clocking in)
    • Onboarding waves (many new hires on the same day)
    • Payroll period processing (end-of-period spikes)
    • Benefits enrollment waves
    • Scheduled batch processing windows

    Long-running workflows:

    • Multi-step orchestration across systems
    • Workflows with external API delays
    • Background processing pipelines

  • Larger data storage needs

    • Extended execution history retention
    • Large decision tables or policy rules
    • Compliance and audit trail requirements
    • Custom HR/WFM data for workflow logic

  • Production-critical workflows

    • Workflows supporting core business processes
    • Higher reliability expectations
    • Workflows that must scale with business growth

When Premium is recommended:

  • You expect many workflows to run simultaneously during peak periods
  • You have approval workflows that accumulate pending executions
  • You process high-volume events (hundreds or thousands per day)
  • You run scheduled batch workflows that create concurrency spikes
  • You need larger data storage for compliance, audit, or custom data
  • Workflow automation is central to operations, not just a pilot
  • Multiple teams across the organization are building workflows

Workflows Add-on

What the Workflows Add-on provides:

  • Additional active workflow capacity
  • Additional data storage capacity
  • Does NOT add concurrent execution capacity

When to use the Workflows Add-on:

  • You've reached your active workflow limit but concurrency is not the constraint
  • You need more active workflows but executions complete quickly (no long wait states)
  • You need additional storage for workflow-related data (decision tables, audit logs)
  • Multiple teams want to publish workflows but concurrency demand remains moderate

NOT needed when:

  • You're hitting concurrency limits (consider Premium or Concurrent Executions Add-on instead)
  • Storage is not a constraint

Concurrent Executions Add-on (Premium Only)

What the Concurrent Executions Add-on provides:

  • Additional concurrent execution capacity
  • Available only with Compose Premium (not available for Base)

When to use the Concurrent Executions Add-on:

  • You're hitting concurrency limits:

    • Workflows are queuing or failing to start
    • Execution history shows many workflows waiting during peak periods
    • Error messages indicate concurrency capacity exceeded

  • You have many approval workflows:

    • Workflows pause waiting for manager or employee responses
    • Pending executions accumulate throughout the day
    • Approval backlogs during busy periods

  • You process event bursts:

    • Shift-start punch bursts
    • Onboarding waves
    • Payroll period processing
    • Benefits enrollment spikes
    • End-of-period batch processing

  • You have long-running workflows:

    • Multi-step orchestration that takes minutes or hours
    • Workflows with external API calls and delays
    • Background processing pipelines

  • Peak period demand:

    • Predictable spikes during specific times (shift changes, end of day, month-end)
    • Seasonal spikes (year-end, benefits open enrollment, mass hiring events)

NOT needed when:

  • Workflows complete quickly (seconds or minutes)
  • Workflows run on predictable schedules with no overlap
  • You have low event volume
  • You don't have approval workflows or wait states
  • You're on Compose Base (not available; consider upgrading to Premium)

Choosing the Right SKU

When to Choose Compose Base

Compose base is best when:

  • You're getting started with Compose
  • You have a small number of focused use cases (single department or limited scope)
  • Your workflows complete quickly (no long wait states or approvals)
  • You don't expect high-volume event processing
  • Workflow automation is experimental or pilot-stage
  • You have modest data storage needs

When to Choose Compose Premium

Compose Premium is best when:

  • You plan to build a larger workflow footprint (multiple departments)
  • You need approval workflows that pause and wait for responses
  • You process event-driven workflows (Pro HCM events, webhooks)
  • You expect workflows to run simultaneously during peak periods
  • You have scheduled batch processing that creates concurrency spikes
  • You need higher data storage for compliance, audit, or custom data
  • Workflow automation is central to operations, not just a pilot
  • You anticipate needing the Concurrent Executions Add-on

When to Evaluate the Workflows Add-on

Consider the Workflows Add-on when:

  • You've reached your active workflow limit
  • You need more workflows but concurrency is not the constraint
  • You need additional data storage capacity

When to Evaluate Concurrent Executions Add-on

Consoider the Concurrent Executions Add-on when:

  • You're on Premium and hitting concurrency limits
  • You have many approval workflows creating pending execution backlogs
  • You process event bursts that strain concurrency
  • You run scheduled batches that create concurrency spikes during execution windows

Capacity Planning Guidance

Questions to inform SKU selection

Workflow portfolio:

  • How many workflows do you plan to build in the first year?
  • Will workflows be concentrated in one department or spread across multiple teams?
  • Are you replacing existing manual processes or creating new automation?

Execution patterns:

  • Will workflows run scheduled, event-driven, or on-demand?
  • Do workflows include approval steps (wait states)?
  • What is your expected event volume? (daily, peak periods)
  • How long do workflows typically run (seconds, minutes, hours)?

Data storage:

  • Do you need to store custom data, decision tables, or audit logs?
  • What are your execution history retention requirements?
  • Do workflows handle binary data (documents, images)?

Concurrency indicators:

High-concurrency signals:

  • Approval workflows (pause while waiting for response)
  • Event bursts (many triggers at the same time)
  • Scheduled batch processing (predictable spikes)
  • Long-running workflows (multi-step orchestration)
  • Real-time event processing (Pro HCM events, webhook triggers)

Low-concurrency signals:

  • Scheduled workflows that complete quickly
  • Simple notification or data transformation workflows
  • Workflows with no wait states or approvals
  • Workflows that run at staggered times (no overlap)

Troubleshooting Capacity Limits

Hitting active workflow limits

  1. Review which workflows are active vs inactive
    • Check execution history to see which workflows ran today
    • Identify workflows that rarely execute
    • Consider deactivating unused workflows
  2. Consolidate similar workflows
    • Look for workflows doing similar tasks that could be combined
    • Use branching logic (IF/Switch) instead of separate workflows
  3. Evaluate Workflows Add-on
    • If you need more active workflows but concurrency is not the constraint

Hitting concurrency limits

  1. Review execution history for peak concurrency periods

    • Identify when workflows are running simultaneously
    • Look for pending executions accumulating during peak times
    • Check for workflows waiting in approval states

  2. Identify long-running workflows

    • Review execution times in execution history
    • Look for workflows with approval steps or wait states
    • Identify workflows with external API calls causing delays

  3. Optimize workflows to complete faster (where possible)

    • Remove unnecessary wait states
    • Optimize external API calls
    • Reduce unnecessary processing steps

  4. Consider capacity upgrades:

    • For Base customers: Upgrade to Premium for higher concurrency capacity
    • For Premium customers: Evaluate Concurrent Executions Add-on

Hitting storage limits

  1. Review data retention policies

    • Check execution history retention settings
    • Identify old execution data that can be archived or purged
    • Review custom data tables for unused entries

  2. Archive or purge old execution data

    • Remove execution history beyond your compliance retention requirements
    • Clean up test or development execution data

  3. Evaluate Workflows Add-on

    • Adds additional storage capacity for workflow-related data

Related Pages

Product overview:

Implementation:

Operations:

Connectors:

Updated 8 days ago