Title: Log Viewer and Job Progress Not Displaying After Initial Login in Katalon Studio 11.5.0
Description:
We are experiencing an intermittent issue in Katalon Studio 11.5.0 where execution logs and job progress are not displayed after the first login of the day.
Environment
- Katalon Studio Version: 11.5.0
- Browser: Google Chrome
- Execution Type: Web UI Automation
Issue Details
After launching Katalon Studio and logging in for the first time, test execution starts and runs successfully. The browser automation can be observed executing as expected, and execution results are available in the Console view. However:
- The Log Viewer remains completely blank during execution.
- The Job Progress panel does not show any execution progress or status updates.
- Test execution itself is not impacted and continues to run normally.
The issue persists throughout the session. The Log Viewer and Job Progress panels do not start functioning correctly until I log out of Katalon Studio and log back in.
Workaround
- Log out from Katalon Studio.
- Log back in using the same account.
- Re-execute the test.
After re-authentication:
- Execution logs are displayed correctly in the Log Viewer.
- Job Progress is updated normally.
- Test execution details become visible as expected.
Frequency
The issue occurs most of the time after the first login, when launching Katalon Studio for the first time.
Additional Information
- Screenshots and a video recording demonstrating the issue have been captured and attached.
- Company-specific information has been masked in the provided evidence.
- An error message is observed during the initial login session. Once I log out and log back in, the error no longer appears and the application behaves normally.
Expected Behavior
Execution logs and Job Progress updates should be displayed correctly immediately after login, without requiring users to log out and log back in.
Actual Behavior
Test execution runs successfully, but the Log Viewer remains blank and Job Progress is not displayed until the user re-authenticates by logging out and logging back into Katalon Studio.
This is the image during execution
This is the image where the console has data
I am deliberately hiding things in the image, so pls excuse
Test execution runs successfully, but the Log Viewer remains blank and Job Progress is not displayed until the user re-authenticates by logging out and logging back into Katalon Studio.
Not sure whether it is a bug or not, but I have posted as I am regularly getting this issue
Known issue with version 11.5.0, fixed in versions 11.6.0 onwards.
As a workaround, go to Project > Settings > Execution, uncheck Enable New Execution Viewer, then restart the test then you should see the Job Progress showing again. You might need to save and close your project and re-open for the change to persist.
By the way, why do you always add separate comments one after another to practically every thread you post in? Kudos farming perhaps? 
I am afraid, this sounds rude to @arvind.choudhary.
I’m not trying to be rude at all, but why open a thread and then spread a post across 8 comments? Seems strange, at least to me.
Don’t think I’m the only person that’s noticed this pattern either.
Thank you for taking the time to read through all my comments and understand the perspectives I am trying to share. However, I feel that consolidating everything into a single, lengthy post may reduce reader engagement, as large amounts of information can be difficult to absorb at once.
To my knowledge, there is no guideline requiring all points to be included in one post. I prefer sharing ideas as separate posts so that each topic receives focused attention. If those contributions also happen to earn me kudos points, I do not see that as an issue, as the primary intention is still to share meaningful insights with the community.
Thanks again, as I added one more comment here, 
But surely, I will stop doing this type of post or this style of posting, as if you are thinking then surely others might also be thinking the same. You need not to bother again for it
