Description

The web UI currently sends two separate requests to the CLP package for each user query:

1. One request for the timeline data
2. Another request for the search results

This causes the search job count to increase by 2 for each query submitted through the web UI, which creates a confusing user experience and unnecessary overhead.

Steps to Reproduce

1. Open the web UI
2. Submit a search query
3. Observe the search job count increases by 2 instead of 1

Expected Behavior

Each user query should ideally result in a single job count increment.

Actual Behavior

Search job count increases by 2 for each query, making it appear as if twice as many searches are being performed.

Potential Solutions to Explore

Consider ways to improve the user experience.

Additional Context

• This is not caused by the web UI itself but appears to be an architectural consideration
• Issue affects user perception of system load and job management
• Reported in PR feat(clp-package): Expose dataset selection in package CLI scripts and web UI.  #1050: feat(clp-package): Expose dataset selection in package CLI scripts and web UI.  #1050
• Original comment: feat(clp-package): Expose dataset selection in package CLI scripts and web UI.  #1050 (comment) api repos/y-scope/clp/pulls/1050/comments --jq '.[-1].id')

Environment

• Component: Web UI + CLP Package interaction
• Affects: User experience and job count accuracy