Forum Discussion
Helper Igetting issue with Project osmos
I was recently testing the project osmos with an f2 capacity got this error after it executed for some 40 mins.I was just testing .Gave this prompt and got the error after execution :
"""
Create a Project Osmos task for the OSMOS_SupplyChain_Lakehouse.
Build an end-to-end supplier performance data engineering solution.
Create a small sample supplier order dataset containing supplier,
material, ordered quantity, delivered quantity, promised delivery date,
actual delivery date, defect rate, shipment mode, supplier rating and
supplier remarks.
Create a bronze layer that preserves the source data.
Create a silver layer that:
- standardizes data types
- handles invalid or missing values
- calculates delivery delay days
- calculates delivery performance
- validates ordered and delivered quantities
- standardizes supplier ratings and defect rates
Create a gold table named gold_supplier_performance containing:
- supplier
- total orders
- total ordered quantity
- total delivered quantity
- average delivery delay
- average defect rate
- delivery performance
- supplier rating
- supplier risk category
Create Spark notebooks required to implement the solution.
Run the transformations in the correct order.
Validate:
- row counts
- null values
- duplicate supplier/order keys
- data types
- delivery calculations
- quantity totals
- gold table output
Do not modify or delete existing user data.
Use new tables and artifacts for this demonstration.
"""
I want to understand that what alternative we can have to use it on a f2 capacity or we need to upgrade to a bigger capacity.
ERROR={"code":"CapacityLimitExceeded","subCode":0,"message":"Unable to complete the action because your organization�s Fabric compute capacity has exceeded its limits. Try again
later.","timeStamp":"2026-10-09T10:40:07.882692Z","httpStatusCode":429,"hresult":-2147467259,"details":[{"code":"RootActivityId","message":"282fd3a5-6245-426e-b5cd-df7656b0025f"}],"exceptionCategory":1}
Failed with exit code 1
2 Replies
- tayloramy
Super User
Hi Anmoldeep,
This error is because your capacity reached its limit. an F2 capacity isn't big enough for a lot of the AI stuff, especially project osmos.
To continue testing, I suggest you either give osmos much simpler tasks to complete, or upgrade your capacity to a larger capacity.
jubinsoniAdvocate IV
Hi Anmoldeep,
I think the key point is that this is not a bug in your prompt. The 429 CapacityLimitExceeded error means the F2 capacity was throttled while a long job was running.
An F2 only has 2 capacity units, and an end-to-end build with bronze, silver and gold layers means several Spark notebooks plus the agent work around them. After around 40 minutes the accumulated usage went beyond what the capacity could smooth, so new operations were rejected. The throttling stages are explained in the Fabric throttling documentation
I would not retry the same big prompt on the same capacity, because the overage from the failed run still has to burn down before new work is accepted. The Capacity Metrics app shows which item used the most CU seconds, so you can confirm it before changing anything. Details are in the Capacity Metrics app documentation
So I would break the prompt into smaller stages like this
Run 1: bronze layer only -> check CU use in the Metrics app Run 2: silver cleanup -> let smoothing settle Run 3: gold_supplier_performance -> validate outputs One big prompt on F2 -> throttled after ~40 min (429)If you only want to see what Project Osmos can do, this keeps each run small enough for an F2 to absorb. If you want the full end-to-end build in one go, a trial capacity or a larger SKU for the test is the practical route, and you can scale back down afterwards.
So I would split the task into stages, check the Metrics app after each one, and only move to a bigger capacity if a single stage still gets throttled. Please let us know how it goes and mark a reply as the solution if it helps.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
