#Agentforce326 debatiendo

Hi Josiah,  

I completed the setup steps immediately after attending Dreamforce.  

My builder central permission set never appeared, nor did anything else in setup related to it.  

After an escalated ticket with support, they informed me it was simply due to their rollout schedule and that my org was scheduled for Oct 2nd at midnight. This must be the same problem you're facing.  

Hi @Sumit Sangwan

Hi Sumit, I think what you’re seeing is expected behavior with the current Voice + connected subagent setup. 

From your testing, it looks like loading_text is always being spoken on the voice channel. When you leave it empty, Agentforce falls back to the default message “Collaborating with other agents”

instead of staying silent. 

outbound_filler_sentences is mainly used while actions are running, so it may not control the connected subagent handoff message. 

At the moment, I’m not aware of a supported value like blank space, null, or another setting that completely removes this audio. 

So your current workaround: 

loading_text: "One moment."

is probably the safest option for now. 

I would also raise this with Salesforce Support or post it as an Idea, because on a live PSTN call, hearing the same handoff message on every subagent turn can definitely affect the user experience. 

Thank you, 

Venkat Yadav.

Hi @Scott Holmes

This looks like an Agentforce Report Analyst issue, not necessarily an issue with the report itself. 

I would try these checks:

1. Make sure the user has the required Agentforce for Sales permissions.
2. Check whether the Data Cloud User permission set is assigned.
3. Test the same report as a System Administrator.
   • If it works for Admin but not for the user, it is most likely a permission/access issue.
4. Check access to the report folder, report type, objects and fields used in the report.
5. Try with a very simple Accounts or Opportunities report.
   • If simple reports work, the issue may be related to that specific report configuration.
6. Also try once in an incognito window or another browser, because the error shown looks like a UI/JavaScript error.

If everything is configured correctly and the same error continues, I would suggest raising a Salesforce Support casewith the screenshot and reproduction steps. 

Thank you, 

Venkat Yadav.

Hi @pankaj singh

This is a server-side problem, and nothing in your org's Setup is likely to fix it. A preflight that returns 204 with no Access-Control-Allow-Origin header from

• Builder Central is in beta and needs the "Access Builder Central" permission set plus the Builder Central Beta feature enabled. You've done both. salesforce
• Developer Edition is supported only with Foundations or Agentforce 1 editions. salesforce
• The release notes say availability started in September 2026. The beta is only weeks old, so a rollout gap for some org types is plausible. salesforce

• A similar pattern appears in a recent CLI issue: an Agentforce Developer Edition org on an orgfarm instance got an empty 404 from an api.salesforce.com authoring endpoint. That is a different endpoint, but it suggests some api.salesforce.com services aren't reliably routed for these DE orgs. github
• The most likely cause is that the dx-workspaces-proxy service isn't provisioned or routed for your org or instance yet. Only Salesforce can fix that.

Quick checks to rule out your side (about 10 minutes)

1. Setup → Company Information: confirm the edition really shows Developer Edition with Foundations or Agentforce 1.
2. Data 360 Setup Home: confirm provisioning shows fully complete, not "in progress". Provisioning can lag after you enable it.
3. Confirm the permission set is assigned to the exact user you're logged in as.
4. Log out and back in, and use a fresh incognito window with extensions off. The curl repro makes this unlikely to help, but it's cheap.
5. Also try opening Builder Central from the App Launcher rather than from Setup.

If those pass, escalate with the details you already have

• Send the endpoint, the 204 with no ACAO header, the Org ID 00DgK00000WFVD2, the Workspace ID, the timestamp, and any x-request-id header from the response.
• Use the in-app "Give feedback" link and your Trailblazer Community post. Developer Edition orgs generally have no support case entitlement, so the community post is probably your best channel.
• Ask specifically whether the workspaces proxy is enabled for your org's instance and region, and whether DE orgs created via the Agentforce signup form are in the beta cohort.

Don't build a workaround around the blocked endpoint, such as a CORS proxy or browser flags. Even if the welcome screen loaded, project creation would still depend on that same backend. 

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi @Scott Holmes

The Unmetered User Based AI permission set license is separate from your Salesforce Sales license. If Digital Wallet shows 1 available license, you should be able to assign that PSL to a user and then assign/create the corresponding permission set. 

Go to Setup → Users → select the user → Permission Set License Assignments and check for Unmetered User Based AI. Then assign the Unmetered User Based AI permission set as well. Both are required for unmetered Agentforce usage. 

If the PSL doesn't appear under the user's available licenses, verify that the required Agentforce add-on/edition is actually provisioned for the org.  

https://help.salesforce.com/s/articleView?id=ai.generative_ai_usage_unmetered_considerations.htm&type=

https://help.salesforce.com/s/articleView?id=005313925&type=1&utm_source

Hope This Helps!!