Salesforce Debug Logs

Working within Salesforce's multitenant environment means that you must consider Salesforce limits whenever you're adding automation to your org. When adding automations to objects that are either part of the Youreka managed package or that interact with the managed package, you must also consider that there are already automations in place that make Youreka work which will also fire.

When encountering issues that could be related to Salesforce governor limits, the Youreka support team may request that you provide Developer logs that give us insight into what's actually happening when you make a change in Salesforce. Here's how!

How to Set Up Debug Logs

1. As a Salesforce Administrator, navigate to Debug Logs in Setup.
2. Click New.
3. Set Traced Entity Type to User
4. For Traced Entity Name select the running user who is able to replicate the error
5. For Start Date and Expiration Date Choose a start and end date and time during which the designated running user will replicate the error. *A large number of logs could be generated, so define the smallest possible window. Every time that user does anything in Salesforce, more logs are generated.
6. For Debug Level, select New Debug Level and define the following settings:
   Name: give the debug level any name you wish, so that you can use it in the future.
   Database: Info
   Workflow: Info
   Validation: Info
   Callouts: Info
   Apex Code: Finest
   Apex Profiling: Info
   Visualforce: Info
   System: Debug
   Wave: Info
   Nba: Info
7. Save.

Generating Debug Logs

During the window that was defined when setting up the debug logs, have the running user you defined replicate the error they're experiencing.

The Salesforce admin should then navigate back to Debug Logs in Setup and delete the User Trace Flag that corresponds to the current Debug Log run. This will stop any additional logs from being generated.

Next Download each debug log generated (there may be more than one page of them). The Support team will either request you share the debug logs, or will review them with you on a followup call.