Skip to main content

Hi everyone, 

 

I’m reaching out to see if anyone has encountered a similar issue. We are an ISV Partner currently packaging our first Employee Agent and our goal is to package only the Subagent and its associated Actions

. Is that feasible? 

 

Here’s what we have done so far:

  1. Created a namespace Scratch Org.
  2. Built an Agent.
  3. Built a Subagent in Agentforce Assets.
  4. Built each Action in Agentforce Assets and linked them to the Subagent.
  5. Added the Subagent to the Agent using Agentforce Builder → Add the Asset from Library.

Issue

After adding the Subagent (with its linked Actions) using Add the Asset from Library, saving the Agent, and attempting to commit the first Agent version, we receive the following error:

The strange part is that the Subagent and its Actions are already configured correctly.

The only workaround we have found is to manually choose the Reference Action, select the correct picklist value again, and save the Subagent. After doing this, we can successfully commit the Agent.

 

Question

Has anyone successfully built a custom Subagent with its associated Actions and then added it to an Agent using Add the Asset from Library

, without having to manually re-select the Reference Action picklist value every time? 

 

We would appreciate any guidance on how to properly package/reference these Agentforce Assets so that the Subagent retains the correct Action configuration and can be committed without triggering the restricted picklist error. 

 

Thanks in advance! 

Error : 'We couldn't commit a version of this agent. Try again or contact your Salesforce admin for help. Source: bad value for restricted picklist field: <reference action>'

 

 

#Agentforce

1 件の回答
  1. 昨日、16:13

    Hi Steffany, 

     

    This looks like a picklist-cache timing issue, not bad data — your workaround (reselecting the same value) confirms it, since the exact same value that failed then gets accepted. 

     

    What's happening: "Add Asset from Library" copies the Reference Action value before the restricted picklist re-indexes the newly added Apex action as valid, so Commit rejects it as "not a recognized value" even though it's correct. 

     

    Try: 

    1. Hard refresh Agentforce Builder after adding the asset, before committing. 

    2. Commit once manually in your source org (fixing the picklist there), then package that already-committed state — so subscribers don't hit it fresh. 

    3. If reproducible from a clean scratch org, file it as a bug via Partner/ISV Support — this is a packaging-specific platform issue worth escalating there. 

     

    Reference:

    https://help.salesforce.com/s/articleView?id=000382161&language=en_US&type=1

0/9000