Support for flows in an LWR site that can contain LWCs was announced in Summer '22. But right now, I can't get that to work, and see a 404 status on the GET of the first LWC embedded in the flow:


with this message reported:

Something went wrong with the "MyComponent" screen component on the "My Flow" flow. Contact your Salesforce admin about this error. LWR3008: Error loading https://abc-def-9876-dev-ed.scratch.my.site.com/MYSITE/webruntime/component/latest/dev/en-US/myNs%2FmyComponent

The site:

  • was setup using sf community create --name MYSITE --template-name 'Build Your Own (LWR)' --url-path-prefix MYSITE templateParams.AuthenticationType=AUTHENTICATED_WITH_PUBLIC_ACCESS_ENABLED
  • appears to be an Enhanced LWR Site
  • has non-flow LWCs working correctly
  • is using 100% LWC components already working in an older Aura template site

The same problem has been reported in these places with no accepted answer posted:

Two questions:

  • Q1: Is there a work-around for this problem?
  • Q2: Does this work at all for you e.g. with no namespaces and no packaging involved?

(I opened a case #46129847 with Salesforce but that did not get me very far.)

  • Is this a regular user or Guest Site User? I know with GSU I had to check the "allow guest users to access public APIs" in Preferences for flows to work, so wonder if it is something to do with that requirement? Jan 24 at 19:21
  • Thanks @BritishBoyinDC; the error is happening for a registered and logged in user for the site. I looked around in the profile and the "process automation settings" but didn't find anything promising. Any other places to look? (The profile is the same one that works in an Aura site.)
    – Keith C
    Jan 24 at 22:02
  • 1
    I have been able to get this to work, as a point of reference: LWR Enhanced SIte Screen Flow => Invocable => Screen with Embedded LWC using results from invocable LWC is just iterating over a list of sObjects Jan 25 at 14:51
  • This issue may be related to the API version. I would suggest upgrading all LWCs to v59.0. It is not directly related, but it may help. "For screen flows that are configured to run on API versions 57.0 and 58.0, on the Process Automation Settings page, select Enable Reactive Components for Screen Flows running API Version 57.0 and 58.0. Add components to your screen, and save and run your flows as usual." Source: trailhead.salesforce.com/content/learn/modules/… Jan 30 at 17:55
  • 1
    Thanks @PabloFischer. Going for 59.0 removes another variable (think this Build Screen Flows with Reactive Components (Generally Available) may be a better link) but making only that change - on the LWCs and the flow - did not fix the problem for me.
    – Keith C
    Jan 30 at 18:44

1 Answer 1


Looks like the cause of my problem is that instead of directly using the flow component I have an LWC (wrapped-flow) wrapping the lightning-flow to improve the startup behaviour e.g. spinner over a card.

If both of these are in the experience page both work. If only flow is in the page it works. If only wrapped-flow is in the page I get the LWR-3008 error. Pretty weird.

On the general areas of "no Aura", this Flows Work with Experience LWR Sites (and why “Navigate Everywhere” and “Open URL” Don’t Work There Yet) explains that some LWC components still layer on top of Aura. So, for example, a LWC that I have that uses lightning-file-upload doesn't render anything for that lightning-file-upload or after that. So somewhat open ended "gotchas" possible.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .