There is a critical inconsistency between the query and mutation for the global userAgentPassThrough setting.

• The updateUserAgentPassThrough mutation correctly updates the dedicated user_agent_pass_through key in the database via systemService.SetUserAgentPassThrough.
• However, the corresponding query in the frontend (systemChannelSettings { userAgentPassThrough }) reads from systemService.ChannelSetting, which is backed by the system_channel_settings database key.

This means that when the user toggles the setting in the UI, the change is saved to one place, but the UI reads from another, so the change will not be reflected upon page reload. The setting will appear to be unsaved.

To fix this, the systemChannelSettings resolver should be updated to correctly source this global setting. A possible fix would be to modify the SystemChannelSettings resolver in queryResolver to populate the PassThroughUserAgent field from systemService.UserAgentPassThrough(ctx).

There's a potential runtime error here. The useUserAgentPassThrough hook can return null, but the setUserAgentPassThroughEnabled state setter expects a boolean. If userAgentPassThrough is null, this will cause an error.

You should handle the null case, for example by coalescing it to false.

The implementation of parseTimeWindow has been changed to use relative time offsets (e.g., now.AddDate(0, 0, -1) for 'day'), which differs from the previous implementation that used calendar-based periods (e.g., start of today, start of this week). This is a significant behavioral change and likely a regression, as it alters the meaning of the time window filters.

The previous logic, which used r.systemService.TimeLocation(ctx) and xtime.GetCalendarPeriods(loc), was more accurate for dashboard time windows as it respected the user's configured timezone and aligned with calendar boundaries. Please consider reverting to a logic similar to the previous implementation.

You will also need to add the following import: "github.com/looplj/axonhub/internal/pkg/xtime".

func (r *queryResolver) parseTimeWindow(ctx context.Context, timeWindow *string) (time.Time, bool) {
	if timeWindow == nil || *timeWindow == "" || *timeWindow == "allTime" {
		return time.Time{}, false
	}

	loc := r.systemService.TimeLocation(ctx)
	period := xtime.GetCalendarPeriods(loc)

	var since time.Time

	switch *timeWindow {
	case "day":
		since = period.Today.Start
	case "week":
		since = period.ThisWeek.Start
	case "month":
		since = period.ThisMonth.Start
	default:
		return time.Time{}, false
	}

	return since, true
}

The initialization logic for the passThroughUserAgent state can be simplified for better readability and conciseness by using the nullish coalescing operator (??).

  const [passThroughUserAgent, setPassThroughUserAgent] = useState<boolean | null>(() => initialRow?.settings?.passThroughUserAgent ?? null);

The logic inside onValueChange can be made more readable by using a switch statement instead of nested ternary operators. This improves maintainability, especially if more options are added in the future.

                              onValueChange={(value) => {
                                let newValue: boolean | null;
                                switch (value) {
                                  case 'enable':
                                    newValue = true;
                                    break;
                                  case 'disable':
                                    newValue = false;
                                    break;
                                  default: // 'inherit'
                                    newValue = null;
                                    break;
                                }
                                setPassThroughUserAgent(newValue);
                                field.onChange(newValue);
                              }}