There is a broken link to a article in the below Trailhead trail
Trail : Prepare for your Salesforce Omnistudio Developer Certification
In the first section : Learn Omnistudio Fundamentals
There is a link to the article "Omnistudio Permission Sets"
The above link is broken and redirect to a blank page
#Create A Case
I am currently working on the Agenblazer Innovator status 2026
While working on the Agentforce Grid -> Explore Data with Agentforce Grid
module i am facing this error eventhough the every configurations are right. Is any agentforce expertice people it would be great to help me!
[LXM001] A temporary system error occurred. Please provide this request ID to customer support. RunId: 01a0d49a-4f08-77ec-ad16-74a1a4242732
Thanks in Advance!
#Create A Case
Hi, see if below solution works
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000jAOj90AGHi,
I tried merging an account to my salesforce one with the purpose of transferring points/status but I don't see the status transferred. Thanks.
#Create A Case #Trailhead
Hi,
I am doing that now - tried this a week back. Initially, was having trouble prompting the AI to truly help but I think I got a human agent on the other end now.
-Fiza
When trying to log into the mobile app, I hit the verify identity button and nothing happens. Has anyone else experienced this?
#Create A Case
Forum Ambassador
help check how is your passkey or MFA definition for your org?
as a workaround.. can you try to login through browser first and then check at mobile app?
i am not able to complete this badge because of this below error..please help me to sort out this. I am not able to edit Customer details.
#Create A Case
Hello @Subramaniam Chandrasekaran
I was able to solve this.
problem statement :
1. Get customer details not available in Agentforce Assets.
2. Though the flow was active but still not showing
Solution :
1. Go to Agentforce Assets.
2. Go to Action - New Agent Action
Select flow
Reference: Get Customer Details
3. Once you create the action with the same api name, it will show in the action
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000alhRl0AI
Hello,
I am facing issue while logging into my org. Also, i am not able to raise the case. Please help
#Create A Case
Hi Harshad,
Happy to help — but need a bit more detail since "can't log in" and "can't raise a case" could each have a few different causes:
1. What exact error do you see when trying to log in (wrong username/password, "org unavailable," locked out, MFA issue, etc.)?
2. Which org are you trying to log into — a Developer Edition, Trailhead Playground, sandbox, or production org?
3. When you say you can't raise a case — is this a Salesforce Support case, or a Case record inside your org as part of a challenge? What error appears there?
A screenshot of either error would help a lot too. Once I have that, I can point you to the exact fix.
In the meantime, here's where you can log a support case directly:
- Salesforce Support (for paid orgs/subscriptions):
https://help.salesforce.com/s/
- Trailhead Help (for Trailhead account, playground, or badge/module issues):
https://trailhead.salesforce.com/helpHello everyone,
I’m having an issue with Salesforce Help that is preventing me from opening a Support Case.
I need to request a correction to my Legal Name in Trailhead Academy so that it exactly matches the legal name shown on my passport. I need to have this corrected before taking a Salesforce certification exam, in order to avoid any issues with my identity verification during the certification process.
My Trailhead account is already connected to my Gmail account. However, when I try to access Salesforce Help and open a Support Case, the My Cases page enters an infinite refresh/redirect loop
and keeps refreshing continuously, so I am completely unable to create a case.
I have already tried the following:
The problem still occurs. In fact, after I log in with my Gmail/Trailhead account, the My Cases page starts refreshing continuously and never allows me to proceed.
Because of this issue, I cannot open the official Salesforce Support Case that I need in order to request my Legal Name correction.
Could someone from the Trailhead/Salesforce Support team please help me with this issue or let me know if there is another official way to contact Salesforce Support
and submit my Legal Name correction request?
I am ready to provide my passport as proof of my correct legal name through a secure Salesforce channel.
Thank you for any help!
#Certification #Create A Case
Hi, Few people reported this issue yesterday. Retry after 24 hours it should be work, There is a possibility that a maintainence is going on.
My Trailhead profile displays my full name correctly, but my Legal Name
is incomplete/incorrect. I would like my Legal Name to exactly match my government-issued ID for certification purposes.
Please let me know the process how to update it.
#Create A Case
#Create A Case
Forum Ambassador
Hello @Kent Hendricks, have you tried setting up a Windows Hello / Touch ID / FaceID phishing-resistant MFA, or testing a physical security key as explained below ?
Sources : Links on about registering one of these possible phishing-resistant MFA Identification verification method (link from Salesforce Help Article) :
Eric
Update which I feel this will be helpful for the community, after a few rounds of Salesforce-Jira integrations, here's what's consistently saved us troubleshooting time:
1. Don’t sync everything: Concentrate on business-critical fields (Case, Bug, Story, Priority, Status, Assignee, Resolution). A leaner scope will result in better performance, lower API usage and less conflicts.
2. Go event-driven over scheduled polling: Keeps Support, Engineering, and Product on the same current data.
3. Map fields before you build: Picklists, Statuses, Priorities, Record Types rarely map 1:1 across systems.
4. Assign source of truth per field: Avoid update loops e.g. Engineering owns Resolution/Sprint, Support owns Customer Impact/Case Priority.
5. Think about API limits. Bulk updates burn your allocation fast. Use batching, retries, error handling.
6. Filter attachments/comments: Not everything should cross systems; filter by visibility, user type or keywords to keep internal notes internal
7. Support multiple Jira projects/instances: Configurable mapping scales better than hardcoded routing logic
8. Monitor failed syncs proactively: Logging + retry queues + alerts catch issues before they silently break workflows
For
Salesforce native appexchange options, Sinergify,a Salesforce Jira connector, handles bi-directional sync without middleware and covers most of this out of the box.
What I have seen from my personal experience:
These are just patterns I've observed across customer conversations and implementations.
#Salesforce Admin #Integration #Jira Integration #Create A Case #Case Management #Salesforce