#Developer Edition Org25 discussing

Yes. Turn on the Einstein generative AI audit data. You can then see the exact prompt that was sent to the LLM, and the exact response, for every call, including the ones fired from your record-triggered flow.

How to see it

1. Setup > Einstein Setup: turn on Einstein Generative AI data collection and storage (audit and feedback data). Data Cloud must be provisioned in the org.
2. Do one real end-to-end transfer again.
3. In Data Cloud > Query Editor (or a Data Cloud report), look at GenAIGatewayRequest__dlm. The maskedPrompt__c field holds the fully resolved prompt that actually went to the model (after Trust Layer masking), and userId__c shows which user the call ran as. The model's answer is in GenAIGeneration__dlm.responseText__c. New records can take a little while to show up.

What to look for

• Compare the prompt from a debug run with the prompt from a live run. Placeholders like <ORDER_NO> and <CUSTOMER_ID> are a classic sign that the model received your instructions but not your transcript, so it wrote a generic sample summary. The audit record will show whether the transcript was really in the live prompt.
• Check userId__c on the live request. When you debug, everything runs as you. In a live transfer, the ownership change is made by routing (the accepting agent, or an automated/system user), so the flow and the prompt template run as that user. Make sure that user has the Prompt Template User permission set and access to everything the template and your Apex read.
• Check that the prompt action's input in the flow is mapped to your Apex output on the path that runs live, not to a variable that only gets populated when you debug.

If you found this answer helpful, please mark it as helpful.

Hello @Omkar Modhave

No, there is no recovery option once a current-generation Salesforce Developer Edition (DE) org has been permanently deleted.  

When a Developer Edition org is inactive for 180 days, Salesforce permanently deactivates it, and it can’t be reactivated. Salesforce Support typically cannot restore expired Developer Edition orgs.

What You Can Do:

1. Request a Backup: Ask Support if they have a backup of your org (rare, but worth a try).
2. Create a New Developer Org: Set up a new org and rebuild your portfolio. Use any saved code or configurations if available.
3. Use a Sandbox: If you have access to another Salesforce org, replicate your portfolio in a Sandbox.
4. Backup Strategy: Going forward, back up your org using tools like SFDX, Workbench, or Git.

https://help.salesforce.com/s/articleView?id=xcloud.admin_de_org_expiration.htm&type=5

Hi @Kandula Hemanth Kumar

Your screenshots narrow this down. I think the problem is that you're using the wrong Salesforce panel, not a broken configuration. 

What the screenshots show 

• Your pane config is fine. The Email Application Pane Default has Related and Tasks tabs with Email Templates, Log Email or Event, People and Contacts. It's the default page and it's assigned to System Administrator. This rules out the "empty pane" theory.
• Cookies and clickjack aren't the problem. Third-party cookies are allowed, and the clickjack settings look normal. Your Incognito test also proved nothing, because Chrome blocks third-party cookies in Incognito, as your own screenshot says.
• The panel in your first screenshot is Chrome's side panel, not the Gmail add-on. It has the Salesforce logo and pin/close buttons at the far right, and your last screenshot shows the same panel. That's the Salesforce Chrome extension, whose home view shows Contextual Insights, My Goals and Search. It works on non-email pages because it's authenticated, as you noticed. It isn't what renders the Email Application Pane, so it stays blank when you open an email.
• The Gmail add-on isn't installed or pinned. In your first screenshot, Gmail's own right sidebar shows only Calendar, Keep, Tasks, Contacts and the "+" button. There's no Salesforce icon. The Email Application Pane (Related / Tasks tabs) appears there, not in the Chrome side panel.

This is an inference from the screenshots, so verify it with the steps below. 

1. Close the Chrome side panel. It's a distraction for this test.
2. In Gmail, click the + in the right sidebar (Get add-ons) and install the Salesforce add-on from the Google Workspace Marketplace. Grant the permissions.
3. Open an email and click the new Salesforce icon in the right sidebar.
4. When the add-on asks you to log in, use the custom domain / sandbox option with your sandbox My Domain URL. Don't use the default production login.
5. Test with an email from an address that exists on a Contact or Lead. Your test email is self-sent, so you may see an empty Related tab even once the pane works.

Other notes

• Cookie exceptions: add [*.]salesforce.com alongside your existing [*.]force.com and [*.]sandbox.my.salesforce.com entries.
• Clickjack setting: you unchecked "headers disabled" only as a test. It didn't help, so restore whatever it was before. I can't tell from the screenshot what the original value was.
• Chrome flags: I'd skip the chrome://flags suggestion from the thread. It isn't backed by your evidence.

One question: is the Gmail account personal (@

) or Google Workspace? I haven't verified that personal accounts are fully supported for the Gmail add-on, and the "Upgrade" button in your first screenshot suggests personal. If the add-on won't install or authorize, that's the first thing I'd check in Salesforce Help. Also confirm in Setup > Gmail Integration and Sync that the integration toggle is on and the user has the required permission set. I haven't verified the exact permission set name. 

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

If you can access the org already I'd just create a new System Admin user and use that to connect to your VS Code. Make sure to use a password manager to store these details for future reference. 

When you're logged in as the new user you could run anonymous apex to force reset the password of your current user if you wanted. (You could probably do this step withotu creating the enw user, but at risk of accidentally locking yourself out I'd make sure you have a second user) 

//Enter username of User to Change
String username = '';
//Set the new password
String password = '';
User u = [SELECT Id
         FROM User
         WHERE Username = :username
         LIMIT 1];
Id userId = u.Id;
System.setPassword(userId,password);