Activity Forums Salesforce® Discussions What to do when I am getting error while updating debug log trace flag in Salesforce?

  • What to do when I am getting error while updating debug log trace flag in Salesforce?

    Posted by madhulika shah on August 24, 2018 at 12:53 pm

    I am trying to update the debug log trace flag for my user but getting the following error:

    Having an active trace flag triggers debug logging. You have 259 MB of the maximum 250 MB of debug logs. Before you can edit trace flags, delete some debug logs.
    I have removed all existing debug logs but it is still throwing the error.

    shariq replied 6 years, 1 month ago 3 Members · 2 Replies
  • 2 Replies
  • shradha jain

    Member
    August 24, 2018 at 12:56 pm

    Hello Madhulika,

    You can  fix it by deleting all debugs logs from developer console.

    1. In dev console, Select tab "Query Editor" at the bottom of the console
    2. Select check box "Use Tooling API"
    3. Use this query:

    SELECT Id FROM ApexLog

    Delete all rows.Once all rows are deleted you will be able to save new debug logs.

    Refer the following link for more information:
    https://help.salesforce.com/articleView?id=000194045&type=1

    Thanks.

     

  • shariq

    Member
    September 17, 2018 at 10:02 pm

    Hi,

     

    For Longer term, the problem comes back to the Summer'18 update Store Larger Debug Logs with Changed Log Limits:

    We increased the size limit for debug logs from 2 MB per log to 5 MB. You can store up to 250 MB of debug logs at a time. System logs are now deleted automatically after 24 hours instead of after seven days. Monitoring logs are still saved for seven days.
    This is also compounded with the Winter '18 update Retain More Debug Logs for Longer:

    We changed the way that we delete old debug logs. We now retain debug logs for 7 days. You can generate a total of 250 MB of debug logs in a 15-minute window. When your org is upgraded to Winter ’18, all logs that are at least 7 days old are deleted. This change applies to both Lightning Experience and Salesforce Classic.

    Hope this helps.

Log In to reply.

Popular Salesforce Blogs

Popular Salesforce Videos