Skip to main content

#AgentforceTesting11 debatiendo

I followed all the step which sugessted in Community and module steps also but still same issue facing.     A temporary system error occurred. Please provide this request ID to custom... 

I followed all the step which sugessted in Community and module steps also but still same issue facing. A temporary system error occurred. Please provide this request ID to custom...

 

#Trailhead Challenges  #Agentforce  #AgentforceTesting

2 comentarios
  1. 14 oct, 14:04

    Hi @Manish Nagar Since the same error is appearing for all Account records, it could be related to the Agentforce Grid configuration or a Salesforce-side issue.

    I would suggest checking a few things:

    1. Test the Summary Prompt Template directly in Prompt Builder.
    2. Verify the Agentforce action and required permissions.
    3. Try generating the summary for a single Account.
    4. If the prompt works individually but fails in Grid, check Salesforce Trust for any service issues.

    If everything looks fine, I would recommend raising a Salesforce Support case with the Request ID and screenshot.

    Hope this helps!

I’m using Conversation-Level Testing in the new Agentforce Studio Testing Center (Beta) on Summer ’26. 

I downloaded the CSV template directly from Upload Test Cases → Template, which contains: 

Conversation, Expected Actions, Expected Subagents 

However, after uploading the populated template and running the test, I receive: 

 

Turn-Level Testing works correctly with its corresponding CSV template. 

  

Is there a different column name or CSV format required for Conversation-Level Testing, or is this a known issue with the current Beta Testing Center? 

  

 

#AgentforceTesting  #Agentforce

1 respuesta
  1. 16 sept, 23:03

    @Bodala Pallavi

     

    What I'd try, quickly - 

    1. Populate the template without opening it in Excel if you can, or re-save explicitly as CSV UTF-8, to eliminate the encoding angle. 

    2. Check the exact header spelling and order against any current Salesforce Help doc for Conversation-Level Testing, in case the tool expects a slightly different header (for example a "Conversation" vs "Conversation Transcript" naming drift between template versions). 

    --> If both check out, treat it as a known Beta issue. Conversation-Level Testing is new in Summer '26 and this is exactly the kind of template-versus-parser mismatch that shows up in Beta.  

     

    Since the template came straight from the tool and Turn-Level works with its template, this points to a Beta bug rather than user error. I'd log it with Salesforce Support, referencing Testing Center Beta, and note that the tool-provided Conversation-Level template is rejected on upload.

Hi everyone,

We are preparing an external API / web application integration for our AppExchange Security Review. The review team will need to test our API endpoints from their automated scanning suites and dynamic networks.

Our main operational blocker right now is MFA and Device Activation (OTP). Because our team does not have personnel available on standby 24/7 to instantly provide multi-factor authentication access codes or email OTP tokens to the reviewers, we need an entirely hands-off authentication architecture for our test environment.

Given Salesforce’s strict platform enforcements restricting traditional UI MFA bypass permissions, what is the current accepted practice for API apps?

My Questions:

  • If we provision a dedicated Salesforce Integration User license (which uses API-only tokens/OAuth instead of interactive UI login), does the Security Review team's automated testing suite natively support this without triggering an MFA or Device Activation challenge?
  • If the review suite requires standard user credentials that trigger an unexpected email OTP, how are partners managing this asynchronously without a 24/7 live operations team to hand over codes?

We want to make sure we architect our authentication flow correctly so that the submission doesn't fail pre-queue validation due to a missed MFA prompt. Any advice from recent submitters would be huge. 

 

#Appexchage Apps

 

 

#Security Review  #Agentforce

1 respuesta
  1. 22 sept, 5:44

    For an AppExchange Security Review, I’d avoid designing around the assumption that an API-only user automatically bypasses every authentication control. The safer approach is to confirm the current review-team requirements for integration credentials and test the exact OAuth/API flow in the submitted environment beforehand. If automated scanners require interactive authentication, Salesforce Partner Support or the Security Review team should clarify the supported testing arrangement rather than relying on manual OTP handling.  Visit here for more information.

I have a Prompt Template that is invoked from a Record-Triggered Flow.

The user who triggers the record-triggered Flow does not have:

  • Prompt Template User permission 

I would like to understand the expected Salesforce behavior:

  1. Is the Prompt Template User permission required when a Prompt Template is invoked through a Record-Triggered Flow?
  2. If the triggering user does not have this permission, will the Prompt Template still execute?
  3. If the Prompt Template executes successfully, will it consume Flex Credits?
  4. Which user's permissions are evaluated when the Flow invokes the Prompt Template—the Flow-running user or the automation/system context?
  5. What is the purpose of the Prompt Template User permission if Prompt Templates can be invoked through Flow?

 

Looking for clarification based on the current Salesforce behavior/documentation for Record-Triggered Flow → Prompt Template

. 

 

#Agentforce  #Prompt Builder  #Mvp-agentforce-prompt-builder-team  #AgentforceTesting

8 respuestas