ଏକ design branch ଉପରେ RENDERING_DISABLED_FOR_DESIGN_BRANCH ଠିକ କରନ୍ତୁ
ଏକ design branch ଉପରେ render କାହିଁକି ମନା ହେଲା ଏବଂ rendering କିପରି ପୁଣି ସକ୍ଷମ କରାଯିବ ତାହା ଜାଣନ୍ତୁ।
If firing a render returns RENDERING_DISABLED_FOR_DESIGN_BRANCH, rendering has been explicitly disabled on that design branch. Every design branch carries a render_enabled flag that is ON by default; it only turns off when someone calls the enterprise API endpoint design_branch/update_rendering_enabled_status with status "disable" — typically organizations that integrate Infurnia into their own pipeline and want to control where ad-hoc renders are allowed. The gate applies however the render is fired: firing by design version resolves that version's branch and checks the same flag. What to check and do: ask the client's org admin or integration owner whether their system disabled rendering on that branch; re-enabling is the same enterprise API call with status "enable" (it uses their enterprise API credentials — the infurnia-access-token, infurnia-email and infurnia-store-id headers). Key scoping facts: this is per-branch, not per-user or per-design — other branches of the same design render normally; and no billing or plan condition produces this error, so do not send the client down a subscription path — usage limits return a different error (the render overage cap message).