Workflow trigger from app failing with Path not allowed error

💬 Workflows
1

@ChiEn I don’t know if this is related, but I’m getting ‘Path not allowed’ errors when trying to use a workflow inside the new app editor.

Claude responds with: ‘One important finding: I could not run the workflow from my own test-execution context — every workflow call (including a harmless getSchema() on other workflows) fails with "Path not allowed", while normal SQL resource calls succeed. This looks like a restriction on triggering workflows from the agent's execution sandbox specifically, not a problem with your params or the workflow itself.’

This worked a couple of weeks ago when I first linked a workflow into a new app, but it now fails. Has something changed recently?

1 Like
Resource authorisation changes broke our new apps
2

Hello @ash-c welcome back to the Community, Ashley! :grinning_face:

I've moved your question to a new topic since it seems like a separate issue, and I'll address it here.

3

I am facing the same issue.
I am the organization admin with universal access, since yesterday (end of August 17) my app can not execute the workflows and is getting "Path not allowed" and I don’t see any log of running in the workflows. My workflows do semantic search using retool vectors.
I can however manually run the workflows from the workflow page.

4

A workaround would be creating a Restful Api resource and enabling webhook triggers for workflows, then from the app, call the api resource calling the workflows.

5

Welcome to the Community forum @ahrs! Thanks for flagging this @ash-c, and @ahrs for confirming. I've reported it to our engineering team and they're aware and looking into it.

I'll keep this thread updated as soon as I hear back. :folded_hands: