Configure Logging for the Log Analyzer ignores setting the expiration time for a single other user

[Dr. Alexander Hug]

When opening the “Configure Logging” dialog I see all the existing Trace Flags that exists. Usually, all Trace Flags are expired when starting to work, except the Trace Flag for myself.
Refreshing all Trace Flags with the “Refresh” button works great, however, when setting the Expiration Date for a single entry and click on “Save”, the Trace Flag is not updated.

‌

[Scott Wells]

Hi, Alexander. I just tried to reproduce this unsuccessfully. Here are the steps that I followed:

1. Open Log Analyzer.
2. Click the gear toolbar button to open the log settings.
3. In the Trace Flags table, I had three expired trace flags, two for other users and one for an Apex class.
4. Clicked the Expiration Date value for one of the expired user trace flags and selected a new value in the future.
5. Clicked Save and it said that it updated one trace flag.
6. Reopened the log settings dialog and it showed the updated value.

Is that different from what you're doing? It doesn't seem like it, but I wanted to be sure that I'm trying to reproduce this using the same steps.

[Dr. Alexander Hug]

Hi Scott,
I found another hint … looks like I can update Trace Flags that were originally created by myself.
SPC Admin is my user, I can edit two Expiration dates, but the others are ignored.
When updating all Trace Flags with the “Refresh” button all Expiration Dates are updated.

BTW, whats the difference between the “User” and “Developer Log” Type?
Regards, Alexander

‌

[Scott Wells]

Hi, Alexander. Trace flags have a type which one of USER_DEBUG, DEVELOPER_LOG, CLASS_TRACING, and PROFILING. It's not well-documented by Salesforce, but I did find a reasonable description here aside from PROFILING which should pretty obvious:

https://www.forcetalks.com/salesforce-topic/what-exactly-a-difference-between-the-log-types-user_debug-and-developer_log-in-debug-logs/

The lead on updating trace flags created by other users is probably solid. I'll play with that a bit and see if there's some authorization error or similar reported in the API response that's just not being surfaced by IC2.