---
schema_version: "1"
id: 478036bfd59e2e296299868354e0da21bb6936264d0e5e93b2574cd3fb646154
title: Implementation Errors
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/troubleshoot-implementation-errors.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-implementation-errors
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1c610aa15b3baa8eabd03b0f278361b7306a707df76a0d3b1b5781b7828ac8ea
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Implementation Errors

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

You might encounter problems when implementing an API.

## Something Failed While Scaffolding an API

Anypoint Code Builder supports scaffolding these schema fragment files if they’re referenced from
API specs:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th></th><th>Avro</th><th>JSON</th><th>RAML</th></tr></thead><tbody><tr><td><p><strong>AsyncAPI</strong></p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>No</p></td></tr><tr><td><p><strong>GraphQL</strong></p></td><td><p>No</p></td><td><p>No</p></td><td><p>Yes</p></td></tr><tr><td><p><strong>OData</strong></p></td><td><p>No</p></td><td><p>No</p></td><td><p>Yes</p></td></tr><tr><td><p><strong>REST</strong></p></td><td><p>No</p></td><td><p>Yes</p></td><td><p>Yes</p></td></tr><tr><td><p><strong>SOAP</strong></p></td><td><p>No</p></td><td><p>No</p></td><td><p>Yes</p></td></tr></tbody></table>

If you add a fragment that isn’t supported, the scaffolder doesn’t add these fragments as project
dependencies when you import the spec from Exchange. However, you can scaffold schemas that are
specified inline within the spec.

If you attempt to scaffold an API that references these types of fragments, you see a message like
the following:

**Something failed while scaffolding API**

The scaffold fails and the flows and other elements aren’t created. To see scaffolding errors,
select **Mule DX Server: Scaffolding** from the list in the output panel.

If you use the iterative approach to scaffold the API (using
[multi-root workspaces](https://docs.mulesoft.com/anypoint-code-builder/imp-implement-local-apis#scaffold-spec-into-project)), the implementation
project folder structure is not created.

To work around this issue, before scaffolding the API:

1.  Add the fragment directly to a folder in your API spec project, such as `fragments`:

    ![Fragment folder in the Explorer view](/mulesoft/current/en-us/anypoint-code-builder/_images/troubleshoot-imp-scaff.png)

2.  Change the path to the fragment from Exchange to the local folder, for example:

    - Reference Local OAS Fragment

    - Reference OAS Fragment on Exchange

    ```YAML
    $ref: fragments/frag-defs.yaml#/components/examples/flightsList
    ```

    ```YAML
    $ref: exchange_modules/e91cab06-650b-4634-9c6f-5bc4f4fc4d17/frag-defs/1.0.0/frag-defs.yaml#/components/examples/flightsList
    ```

3.  Re-scaffold the API.

See
[Create and Add a Fragment Directly in Your Spec](https://docs.mulesoft.com/anypoint-code-builder/des-create-api-fragments#create-add-fragment-directly).

## See Also

- [Implementing OAS, RAML, AsyncAPI, and GraphQL APIs](https://docs.mulesoft.com/anypoint-code-builder/imp-implement-api-specs)

- [Iteratively Design and Implement APIs](https://docs.mulesoft.com/anypoint-code-builder/imp-implement-local-apis)

- [Known Issues](https://help.salesforce.com/s/issues)