How to capture Symphony logs in Salesforce

There are several ways to track and view the logs for Symphony and its related actions from within Salesforce.

Create User Trace to track platform events

For Flows, you will need to first create a User Trace Flag for the Automated Process user in the Debug logs. Navigate to Setup and search for Debug Logs (Figure 1):


Figure 1 Debug Logs

Select New from User Trace Flags (Figure 2):


Figure 2 User Trace Flags

Inside your User Trace, complete the following information as shown in Figure 3:

  • Set an Expiration Date that gives enough time to run your scenario.
  • Select Debug Level = SFDC_DevConsole by selecting the loop icon.


Figure 3 Debug Levels

Note: A User Trace Flag will be created for the Automated Process user that actually runs the Flows.

Run your Flow and retrieve the debug logs

Once you’ve run your Flow, your logs will be displayed as shown in Figure 4: 


Figure 4 Debug Logs

Select the logs related to the Automated Process user.

View logs of executed apex code of LWC

To view the logs of the executed apex code of LWC, select the Settings icon (Figure 5):


Figure 5 Settings

Select Developer Console (Figure 6):


Figure 6 Developer Console

A separate tab will open displaying the Developer Console (Figure 7):


Figure 7 Developer Console

Select the Logs tab and the log should start to populate as actions are performed on the LWC, for example opening or submitting an item (Figure 8):


Figure 8 Logs

Note: Some logs are triggered by validation processes and other tools rather than the LWC.

When a log with errors, is located, send all the new logs created after this action to the Symphony Support team at

Note: If the files are too large to email, inform the Symphony Support team. They can arrange to receive it using a secure file transfer site, Filevault.

View the trigger and record triggered Flow logs

After updating a record, two or more logs will be added. The main log, which is longer, is the trigger execution log, followed by the record triggered Flow logs.

Locate an issue in the bot logs

If no logs are failing, the issue could be due to the connectivity of the bot, for example the emp connector may need to be connected again. Reconnect the emp connector by following these steps:

1. Open the Admin tab of the Salesforce app.

2. Select your organisation.

3. Add a letter to the username of the emp conector.

4. Select Save.

5.  An error should appear as the username is now incorrect.

6. Close the error banner.

7. Remove the letter added to the username in step 3.

8. Select Save.

Alternatively, an issue could have happened within the bot itself, therefore the bot logs should be retrieved to determine the issue.