fabric-spark-compute-remediatelisted

# Microsoft Fabric Spark Compute remediate Structured diagnostic workflows for resolving Apache Spark compute issues in Microsoft Fabric Data Engineering and Data Science workloads. ## When to Use This Skill - Spark jobs fail with HTTP 430 throttling or TooManyRequestsForCapacity errors - Notebook or Spark job sessions are slow to start (>30 seconds) - Environment publishing fails or hangs - Autoscale is not scaling up or down as expected - Jobs are queued indefinitely or expiring after 24 hours - Custom pool creation fails or pools are undersized - Library installation causes session startup delays - Capacity appears exhausted despite low job counts - VNet/Private Link provisioning adds unexpected delays - Burst factor or job-level bursting behavior is unclear ## Prerequisites - Workspace Admin or Capacity Admin role in Microsoft Fabric - Access to the Monitoring Hub for active Spark sessions - Access to Workspace Settings > Data Engineering/Science - Knowledge of current Fabric capacity SKU (F2 through F2048) ## Quick Diagnostic: Identify Your Issue **Start here.** Match your symptom to a diagnostic path: | Symptom | Diagnostic Path | |---------|----------------| | HTTP 430 error | See [Throttling and Concurrency](./references/throttling-and-concurrency.md) | | Jobs stuck in queue | See [Throttling and Concurrency](./references/throttling-and-concurrency.md#job-queueing) | | Slow session startup | See [Session and Environment](./references/session-and-environment.md