CORS error

MindStudio IDE Bug Reports
1

Been pulling my hair for a week now. Didn’t dawn on me to open the dev console in Chrome before now, for some reason.

  1. Describe what happens in as many details as possible.

On running a second workflow from main workflow, using the ‘Run workflow’ block, the run has consistently failed during image generation. Array with items look good to launch and MS debug log says it contains the correct amount of items. I’m still thinking it’s me being confused over variable handling when running another workflow, but also saw this CORS error that tries to load the agent’s image:

Error from Chrome dev tool:
‘’’
/agents/novelista-valborg-1c5da84e/run?draftVersionId=8d0ca885-f372-48f6-a8b2-18ba4ee90059:1 Access to fetch at ‘https://images.mindstudio-cdn.com/e142cb2f-e45f-429b-8cb5-2ad7fdfa5dec/generated-images/86c98b3a-45a7-4e59-8f19-081bf21b5a62.webp?fm=auto&ar=1:1&fit=crop’ from origin ‘https://app.mindstudio.ai’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
images.mindstudio-cdn.com/e142cb2f-e45f-429b-8cb5-2ad7fdfa5dec/generated-images/86c98b3a-45a7-4e59-8f19-081bf21b5a62.webp?fm=auto&ar=1:1&fit=crop:1

Failed to load resource: net::ERR_FAILED
/favicon.ico:1
Failed to load resource: the server responded with a status of 404 ()
‘’’

Mixpanel errors also.

  1. Describe the intended behavior.
    Workflow should run and images should be generated.

  2. Share a link to AI Agent where this bug occurs
    Agent ID: 41e3d970-93b0-46ba-b26c-3e01486c8685

  3. Attach any screenshots/screen recordings to help us replicate and run tests on our end

    image
    image1693×334 48.9 KB

2

Hi @per,

Thanks for bringing this up. Though it looks like the error is related to the AI Agent favicon, not the failed Runs.

The most likely cause is incorrect variable references in the Run Workflow block. Here are a couple of resources that might help:

If you can share some screenshots or a Loom of your setup, including the Run Workflow block configuration and a sample run in the Debugger, that would help us see what’s going on.

3

Thanks Alex,

It was JSON and variable confusion. I’m not really adept at juggling json yet, but the solution was to have an LLM take the array output from the first “Run Workflow” block and create a new JSON array with a “mother key” so I could pass {{get arrayVar2 “$.content”}} into the second “Run workflow” block. Anyhow, solved it! :wink:

Take care,
Per

2 Likes