Another developer or an automated CI/CD pipeline triggered a build without you realizing it.
SUP0108: A deployment or update operation is already in progress. Wait for the operation to conclude and then re-try.
The error is usually a symptom of a stalled background process. In most cases, a service restart is the best and fastest resolution. If you are in a production environment where a restart isn't possible, checking the database locks is your next best bet.
"status": "started", "request_id": "abc-123" Another developer or an automated CI/CD pipeline triggered
Navigate to your Cloud Portal and look at the Deployment History . Look for any task with a status of "Scheduled," "In Progress," or "Cancelling."
| Practice | Implementation | |----------|----------------| | Serial deployments | Use pipeline queuing to avoid concurrent runs to the same org. | | Timeout settings | Set explicit timeouts (e.g., --wait 30 in SF CLI). | | Heartbeat mechanism | For long‑running deploys, keep the session alive. | | Monitoring | Alert on deployments exceeding normal duration. |
Dell has released firmware versions (such as iDRAC9 v7.20.10.50 ) that specifically resolve bugs where the update job fails to start or reports incorrect "busy" statuses. The error is usually a symptom of a
: Ensure that all settings in Configuration Manager are correctly configured. This includes checking the Software Update Point, distribution points, and any specific collections or deployment settings.
Keep the serverlog.txt open while deploying. This allows you to see if a deployment has actually stalled or if it's just taking a long time.
The SUP prefix designates a within the Dell Extended Error Message (EEMI) ecosystem. The Lifecycle Controller generates this warning when it believes a separate update or staging action is active. The three primary causes are: In the right-hand Quick Links panel
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
: Navigate to the iDRAC Dashboard. In the right-hand Quick Links panel, click Reset iDRAC . Via SSH/CLI : Run the command: racadm racreset Use code with caution.
The iDRAC firmware installer creates a temporary RAM drive on the host OS to run updates; if it doesn't clear properly, subsequent updates are blocked.
The error code is a common and frustrating issue encountered by system administrators managing Dell PowerEdge Servers . This error usually triggers within the Integrated Dell Remote Access Controller (iDRAC) or Lifecycle Controller (LC) interface during firmware updates or virtual media deployments.