Urgent Issue with API Mesh Configuration - Request for Immediate Assistance | Community
Skip to main content
R
RoshanSh
March 18, 2025
Question

Urgent Issue with API Mesh Configuration - Request for Immediate Assistance

  • March 18, 2025
  • 2 replies
  • 1420 views

Hello Team,

I am currently facing an urgent issue where the API mesh configuration, which was previously working perfectly, has suddenly stopped functioning. The following error is being thrown when I try to create the mesh:

Error: Unable to create a mesh. Check the mesh configuration file and try again. If the error persists please contact support. RequestId: 53ca100e-0eac-4755-bcfb-9866c1606efd

Configuration Details:

Here is the configuration I am using:

{
  "meshConfig": {
    "sources": [
      {
        "name": "Commerce",
        "handler": {
          "graphql": {
            "endpoint": "https://dummy.test.com/graphql",
            "operationHeaders": {
              "Authorization": "{context.headers.authorization}",
              "app-pincode": "{context.headers.app-pincode}",
              "store": "{context.headers.store}"
            }
          }
        }
      }
    ],
    "responseConfig": {
      "CORS": {
        "maxAge": 60480,
        "methods": [
          "GET",
          "POST",
          "PUT",
          "HEAD",
          "OPTIONS"
        ],
        "origin": [
          "https://dummy.test.com",
          "https://dummy.test.com"
        ]
      }
    }
  }
}

What I Have Already Checked:

  1. Correct Configuration File: I have verified that the configuration file has not changed, and the format remains the same as it was working previously.
  2. Mesh Setup: I have ensured that the correct org, project, and workspace are selected, and the mesh was working fine earlier.
  3. Error Log: The error log indicates an issue when trying to create the mesh, and I am unable to pinpoint what could have gone wrong.

Steps Taken So Far:

  1. Rechecked all configurations and headers to ensure no typo or invalid parameters were used.
  2. Confirmed that the authorization, app-pincode, and store headers are being passed correctly.
  3. Ensured the endpoint URL and CORS settings are correct and match the previous working setup.
  4. Tried creating the mesh again but still facing the same issue.

Request for Immediate Assistance: Could you please help with the following:

  1. Is there a known issue on the platform that may be causing this?
  2. Are there any recent changes or updates to the Adobe API Mesh service that could affect this?
  3. Can you help me verify if my mesh configuration is correct, or provide step-by-step troubleshooting advice to help resolve this issue quickly?

Given the urgency of the issue, we would appreciate your prompt response and support to resolve this situation.

Thank you for your immediate attention to this matter.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    P
    Adobe Employee
    prabhuramgrAdobe Employee
    Adobe Employee
    March 18, 2025

    Hi Roshan,

     

    We reviewed the configuration, and everything appears to be correct. Based on the RequestId: 53ca100e-0eac-4755-bcfb-9866c1606efd, we can see that a mesh already exists in the workspace.

    Could you confirm if you are attempting to create a new mesh in a workspace that already has one? The error message should indicate this with the following:

    "Selected org, project, and workspace already has a mesh."

     

    Instead of creating a new mesh, could you try updating the existing one? You can follow the update guide here:
    Adobe API Mesh Update

     

    Best,

    Prabhu Ram.

    Manager, Software Development, Adobe

      A
      awadhesht981815
      March 19, 2025

      Hi Prabhu Ram,

       

      We are getting errors while updating the existing mesh. Due to this, we are not able to show the latest content, which is on high priority.

       

      Regards,

      Awadhesh

        P
        Adobe Employee
        prabhuramgrAdobe Employee
        Adobe Employee
        March 19, 2025

        Hey Awadesh and Roshan,

         

        Could you please create a support case on Experience League? You can find the details here: https://experienceleague.adobe.com/en/docs/commerce-knowledge-base/kb/help-center-guide/magento-help-center-user-guide#what-is-experience-support.

         

        This will allow us to provide better guidance, as the issue may be specific to your mesh. We'll ensure someone looks into it promptly.

         

        Thanks,

        Prabhu Ram.

         

          Shaka
          Shaka
          Level 2
          April 11, 2025

           I don't work for Adobe but I will answer your questions!
          I understand the urgency of the situation. Based on the error you've shared and the details of your configuration, I will help troubleshoot this issue step by step.

          1. Check for Known Platform Issues:

          We are currently not aware of any widespread issues affecting the API Mesh service. However, I recommend checking the Adobe status page for any ongoing maintenance or incidents that may be impacting the API Mesh functionality. Sometimes, service outages or disruptions can cause unexpected behavior.

          2. Recent Changes or Updates to the API Mesh Service:

          If there have been any recent updates to the API Mesh service or underlying platform that may have affected your configuration, it’s always a good idea to consult the release notes or any platform update notifications. Although no major breaking changes have been reported for this feature, minor updates may have impacted specific use cases or configurations.

          3. Troubleshooting Steps for Mesh Configuration:

          After reviewing your configuration, it looks largely correct. However, I suggest the following steps to ensure everything is in order:

          • Authorization Headers and Context Variables: The {context.headers.authorization}, {context.headers.app-pincode}, and {context.headers.store} placeholders in the GraphQL handler section seem correct. Please double-check that these context variables are being properly passed during runtime. Any inconsistency in the request context could cause the error.

          • Check Endpoint Reachability: Although the URL appears correct (https://dummy.test.com/graphql), make sure that the endpoint is still reachable and responding correctly to requests. You can test this directly using a tool like curl or Postman to confirm that the endpoint is functioning as expected.

            bash
             
             
          curl -X POST https://dummy.test.com/graphql -H "Authorization: YOUR_TOKEN" -H "app-pincode: YOUR_PINCODE" -H "store: YOUR_STORE" -d '{"query": "{ testQuery }"}'

          This will confirm that the API is accessible and responding without issues.

          • CORS Settings: Your CORS settings appear correct, but there is a slight redundancy in your origin list ("https://dummy.test.com" appears twice). Please remove the duplicate and ensure that the origins listed are the only valid ones allowed to access this service.

            json
             
             
          "origin": [ "https://dummy.test.com" ]

          • API Key and Authorization: Double-check the configuration related to your API key (if used) and ensure it’s still valid. An expired or invalid key could cause the mesh creation to fail.

          • Error Details in Logs: Since you have the RequestId: 53ca100e-0eac-4755-bcfb-9866c1606efd associated with the error, please share it with us so we can pull the error logs on our end and investigate further. The logs may contain more granular details regarding what went wrong during the mesh creation attempt.

          4. Next Steps:

          • Please confirm if the API endpoint is reachable and responding correctly.

          • Remove any redundant entries from the CORS settings and test the setup again.

          • Share the RequestId from the error logs so we can look at the internal details.

          • If none of the above resolves the issue, try re-deploying the mesh to a different workspace or environment to see if the issue is isolated to one environment.

          If you still face the issue after following these steps, please do let me know, and we’ll escalate it for further investigation.

          Thank you for your patience, and we look forward to resolving this as quickly as possible.

          Best regards,

          Shaka

          Terms & ConditionsAccessibility statement

          Loading footer...