`Run now` creates inconsistent session visibility and does not update last run.

[sangee2004]

Describe the bug
Manually triggering a scheduler with “Run Now” results in inconsistent session behavior. In one case, the session appears in the Sessions list, but its chat view is not displayed; in another, the session does not appear in the Sessions list at all, though it is recorded in Runs. Additionally, manual runs are not reflected in the scheduler’s “Last Run” field, causing inaccurate run tracking.

To Reproduce
Steps to reproduce the behavior:
Scenario 1:

1. Go to Launch Agent
2. Create a Scheduler
3. Wait for the task to be triggered.
4. Go to the Scheduler option
5. Use the Run Now option from the Scheduler list.
   Notice that when the task is run, we see the session relating to the task shown in the Sessions list but the chat view for the session is not shown.

https://www.loom.com/share/72801dc6c00f46f4bcca7c0bf3f0e182

Scenario 2:

1. Go to Launch Agent.
2. Create a Scheduler
3. Wait for the task to be triggered.
4. Go to the Scheduler option
5. Select the scheduler from step 2.
6. Use the Run Now option in the scheduler detail page.

Notice that when the task is run, we don't see the new session relating to the task getting shown in the Sessions list view.

It is shown in the Runs list . Also, Last run does not reflect the manual runs done using Run now. Do we expect to account for the manual runs done as well?

https://www.loom.com/share/8158df06644e49f29277d69d5b2fbe00

Expected behavior
In both scenarios, ideally, we expect the session created from Run Now to be selected in the Sessions list, and the chat view should be displayed for this session.
Last Run for the Scheduler should also account for manual runs performed using Run Now.