Developer forum

Forum » Integration » Improve log UI of scheduled tasks

Improve log UI of scheduled tasks

Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

Hi there,

I find the UI for running scheduled tasks quite cumbersome. There's a lot of info on the UI that I don't need while running the task, while the info I do need is not there. Below is an image of the UI and here's an overview of what's bothering me:

1. When you start the task, you see the old statuses still. I know these are prior runs but everytime I see the Failed status or an exception, I think it's the current job.

2. There's exactly one line for the output, hiding all previous messages (the stuff at the bottom of the image)

3. Even that one line still doesn't show much. More than two thirds of that line are taken up by the task name and date/time whereas the one meaningful message is clipped.

4. The See more view is nicer, but doesn't auto-refresh like the small log section on the overview screen does.

5. The See more view also shows only a part of the log message. Can the log message be multi-line and show more or all of the text? I now need to hover over each line or click it to see it in full.

6. It would be nice if the See more view would automatically be opened when you run the job, and then auto-refresh. That would solve most of the UI issues.

Thanks!

Imar


Replies

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

Furthermore, the full XML from the task is included in the logs. In larger integrations, with paging enabled, this causes tons of XML to be sent to the client. In a current job I am running, I see 1.7 MB being downloaded every 10 seconds and the file size continues to grow with each new ERP data page.

 
Rasmus Sanggaard Dynamicweb Employee
Rasmus Sanggaard
Reply

Hi Imar,

The complexity of the scheduled task overview has increased with the introduction of subtasks. What we've tried to do is keep the information about the main scheduled task at the top, and the specifics of the subtask logs at the bottom. So what you're seeing at the top, called task execution, is only related to the main scheduled task and provides a summary. If you then want to find out in detail what happened, you need to dive into the log history and look at the specific subtasks.

In your example, you only have one subtask, so the task executions become less useful.

It's correct that if you want to see the log message across multiple lines, you need to open it or hover over it — but you can also resize the column. I don't think allowing multiple lines for the message in the list screen would make sense, since we can have very large messages and would still need to truncate them at some point.

We will look into improving the logs so we don't clog some up in large integration jobs.

If you have some specific feature requests for the way we are structuring the scheduled tasks, you can add them to our GitHub, which is the place we handle that.

BR
Rasmus Sanggaard

 

You must be logged in to post in the forum