Developer forum

Forum » Integration » Job errors not shown from scheduled task

Job errors not shown from scheduled task

Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

Hi there,

I have an activity that fails with a message like this:

2025-10-03 14:19:47.2543|DataIntegration|INFORMATION|Error: One or more errors occurred. (The given value of type String from the data source cannot be converted to type nvarchar of the specified target column.)Row data

I know why (the data source sends the value 7500 for the two-letter country code). But when I run this activity from a scheduled task, there's no mention of the error. All I see is this:

I then have to hover over each line in the hopes to find the issue. Then one of them has this:

Yay! A hint. Now., all I need to do is open Assets, find the logs folder for this job and find the log file by its very long name which I also can't copy from the UI. Stuff like this takes me minutes each time instead of seconds.

I really feel that the Integration UI (Activities and Scheduled Tasks) is a major step back in DW 10. Just building activities and tasks takes me far longer than it used to take on DW9. The UI is difficult to use, information screens aren't that informational anymore and distract me with a lot of crap I don't need, while burying the stuff I do need behind 20 clicks.

Am I the only one having issues with integration in 10 or are others suffering from the same problems?

Imar


Replies

 
Michael Knudsen
Reply

Hello Imar,

- I totally agree, for those who works with the Integration UI it's a big pain especilly doing a new configuration/development of an integration. Also in cases like yours, where the job have failed, why isn't there a direct link to the log file? 

Br. Michael Knudsen

 

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Reply

Hi Imar,
that wil be fixed in #25706. You can add more information for the other issues you have, then we can look on how to make it better.
BR, Dmitrij

 
Rasmus Sanggaard Dynamicweb Employee
Rasmus Sanggaard
Reply

Hi,

I know it can feel like a pain when moving from a familiar system to a new one like DW10. One reason is that DW10 is built on a common framework, whereas DW9 had screens built specifically for each area. While this may result in a few more clicks, we've gained significantly in terms of performance and stability.

We've conducted UX and efficiency tests, and the conclusion was that DW10 is just as efficient as DW9—you just need to get familiar with the new way of doing things.

If you have specific feature requests for improving the logs, please add them to GitHub.

BR Rasmus Sanggaard

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

I can definitely see the benefits of the new UI and I often find that it works well. However, currently setting up new integrations is a pain and takes more time than it did on 9, even when factoring out unfamiliarity with the new ways of doing things. I think it's a combination of a couple of things:

1. Logs are difficult to work with. I don't see the logs / problems in a single unified UI anymore and need to consult different places and log files. Also, the current log file browser is difficult to use. I reported these as separate issues and at least that last one is being worked on.

2. A number of bugs: 25645 (fixed), this one (new), 25833 (fixed), 25597 (fixed) and new ones like Primary Keys on mappings not migrated when opening a DW9 job in 10 (not reported yet) make working with integration time-consuming. I appreciate your responsiveness in fixing these issues, but it also takes a lot of time to run into them, understand and report the issue and then wait for a release with the fixes.

3. The ability to see important things at a glance. In 9, the toolbar next to the mapping was super helpful:

With a few clicks, you could see Conditionals, Table scripts and primary keys across all mappings. 

In 10, this takes a lot of scrolling up and down and left and right, especially with large jobs. If you have multiple mappings, the different mappings are hard to distinguish as only the header of each new mapping has a different background color. I know the ellipsis menu for each mapping provides access to these features (as well as showing some of them in the grid) but with multiple mappings with a large number of columns, these are pretty hard to reach. This makes getting an oversight of a new job pretty cumbersome.

There are also things that work well: being able to see the script type and value and null handling in the columns great is really helpful, for example.

Imar

 

You must be logged in to post in the forum