Skip to main content

#Check2 debatiendo

*** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ****** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ***Salesforce is limiting how Managed Runtime (MRT) determines production enviSalesforce is limiting how Managed Runtime (MRT) determines production environments. Currently, you can set any environment to production, regardless of whether it’s connected to an instance. This creates a lot of traffic, which harms the accuracy of monitoring and incident response for everyone on the platform.

 

To reduce traffic and improve capabilities, Salesforce is limiting which environments can be flagged as production. Starting September 29, 2026, an environment can be flagged as production only if it’s associated with a Staging or Production B2C Commerce instance.

 

Log Center logs and Log Center metrics aren't affected by this change. Both stay independently configurable on any environment, regardless of instance tier.

 

To keep production monitoring and related features on these environments, associate each one with a Staging or Production B2C Commerce instance before September 29, 2026.

 

  1. Open Runtime Admin and go to the Environment Settings for the environments listed above.
  2. Associate the environment with a Staging or Production B2C Commerce instance.
  3. Confirm the production flag is still on after you save the association.
  4. Redeploy the current bundle in that environment. This ensures the change takes effect immediately rather than waiting for your next scheduled deployment.

If you don't associate an instance by the deadline, you will lose production monitoring. Your Log Center logs and Log Center metrics settings won't change.

 

Need help?

Contact Salesforce Customer Support if you have questions about which instance to associate.

 

#B2C Commerce #B2B Commerce

2 comentarios
0/9000

I haven't looked too much to see if someone's already done this, but I created a script (see attached) that does the following (this script follows Tableau's documentation here):

  • Creates two folders on your backup system, one folder for each week: current week, and previous week
  • Sets flags that are in email portion of script at the end of script
  • Checks to see if backup schedule already created, if it's not, than it's created (doesn't actually run the backup command); if backup file is created, move it to backup system
  • Create config. and topology data file, and move to backup system
  • Create misc. data file, and move to backup system
  • Create logs backup file, and move to backup system
  • Clean up logs
  • Email Tableau Server admins. with status

 

This is a PowerShell script, and it's scheduled in Windows Task Scheduler.

 

I'm sure there's much more we can do (especially regarding the currency of the backup, and how far back to keep our backup, etc.), but this is a start :) Feedback is much appreciated.

3 respuestas
  1. 3 sept 2023, 4:15

    @Ryan Calovich​  Look ok. But you can refer to the attached powershell script created by me. Preety old but covers everything I guess.

    P.S. If this post resolves the question, would you be so kind to "Select as Best"? This will help other users find the same answer/resolution and help the community keep track of answered questions. Thank you.P

0/9000