latest posts

Hi Nikolaus,
Looked up through dotnet docs, and it seems like it's default limit of connection duration for HttpClient class which is internally used for REST actions.
Seems like automations execution time limit doesn't override that limit too.

I'm not aware of any configuration which webcon gives to override this default value unfortunatelly.

* https://learn.microsoft.com/en-us/dotnet/api/system.net.http.httpclient.timeout?view=net-8.0

On the solution - maybe using Run a PowerShell script action would help - handle that request using a PowerShell script, and just call that script from Webcon? However i'm not sure if you need some kind of response from the service.

Hi all!

Maybe this question has already been answered before, but I am struggling with an automation and action 'Invoke REST webservice'.

I want to start REST API endpoint within a cyclical action on a daily schedule.

This is some kind of 'long running operation', at the moment it takes 10 minutes on PROD environment.

I already set execution time limit to 6000 for automation and also in global configuration, this should be fair enough.

But all I am getting is HttpClient error message after 100s.

Any ideas on how to solve this problem?

Thanks a lot in advance & best regards, Nik

Hi,

It seems there might be an issue on the infrastructure level. We haven't received any similar reports from other users, so it may be specific to your environment.

Could you please check if you're able to connect to googleapis.com from your setup?
If you're using a proxy, please also verify that your proxy configuration allows access to external services.

Best regards,
Łukasz

I used JS button to InvokeRule(Form rule). Form rule used FOR EACH ROW function on Item list to populate technical column with increment integer (1, 2, 3…). This integer was used for Item list sorting in Item list configuration. While in version 2022, the execution order of FOR EACH ROW was driven by sorting (even unsaved) Item list as seen on the screen (First sorted visible row first, Last sorted visible row last), it is not the case in version 2025. What is the driver for FOR EACH ROW execution order over Item list rows now? How can I control it? I used this functionality for users to fix their preferred sorted item list order between savings of partial changes (action needed in process). How to achieve the same behavior/functionality as described in version 2025?

Hi Łukasz, thank you for your response :)

I’ve upgraded to version 2025.2.1.91 as suggested, but I’m still getting the same error.

What other configuration details should I provide to help diagnose the problem?

I would add to this, that instead of saving whole URL you could consider saving only id parts of the url, and then using data row to concatenate whole address.

So a column external_id would store 123456, and inside data row, you could do SELECT CONCAT('https://some_website/some/path/to/resource/', '{external_id}'),
this way you are safe in case that the domain changes in the future, and as a side effect it also uses less space in the db, as link is constructed on display.

Hi Ondrej,

you are right, the Hyperlink function doesn't support long URLs but you could use a data row an return a link using the anchor tag element:


select '<a href=" ...">Displayname</a>' as Link

Best regards,
Daniel

Hi Maks,

yes, that's the one.
The DesktopEndpoint /api/nav/db/15/element/299/deskto also returns the attachments which have just been added to the instance.

Best regards,
Daniel

Hi community,
We are using in our company long URL (especially for SharePoints) with length over 256 characters. Using Item list Hyperlink column with format 'link:http://intranet.company.com;displayname:Link' ends up for long URL to appear as full URL (in Edit mode) instead of displayname. Any Idea how to solve it and show displayname for long URL?

Whoa, that's a nice idea, to be sure, just to make sure are you talking about this endpoint: https://webcon-dev/attachments/db/{db_id}/preview/{att_id}?