03.04.2025
09:14
Hi everybody,
I have a repeating "unmotivated" error message (see attached). It is only in one workflow, always in the transition from one step to the next.
I can't see anything in the history, as you see, there is no error GUID,...
Any ideas, how I could track down that error?
03.04.2025
12:37
Hi,
Have you checked in "Event Viewer" on the server in the "Applications and Services Logs -> WebCon Workflow" node?
Are there any actions connected on the path?
You can disable all of them and enable them one by one to see which one generates such an error.
03.04.2025
13:29
Hi,
Have you checked in "Event Viewer" on the server in the "Applications and Services Logs -> WebCon Workflow" node?
Are there any actions connected on the path?
You can disable all of them and enable them one by one to see which one generates such an error.
Hi Jacek,
in the event viewer, there is noch error that has either a connection to the instance number nor to the time it occurred.
The thing with the actions I will check.
Kind regards,
Klaus
03.04.2025
20:06
Hi Jacek,
in the event viewer, there is noch error that has either a connection to the instance number nor to the time it occurred.
The thing with the actions I will check.
Kind regards,
Klaus
Hi,
Maybe check logs in table Content Database
SELECT *
FROM [dbo].[WFActionExecutions]
where LOG_WFDID =
order by 1 desc
04.04.2025
07:21
Hi,
Maybe check logs in table Content Database
SELECT *
FROM [dbo].[WFActionExecutions]
where LOG_WFDID =
order by 1 desc
Hi,
This message indicates that your request might be taking a long time to complete. Please note that IIS has a default request timeout of 2 minutes.
You can verify the duration of each request using your browser’s developer tools (press F12 in Chrome), then navigate to the Network tab. There, you’ll be able to see if any request exceeds the 2-minute threshold.
Best regards,
Łukasz
07.04.2025
14:32
Hi,
This message indicates that your request might be taking a long time to complete. Please note that IIS has a default request timeout of 2 minutes.
You can verify the duration of each request using your browser’s developer tools (press F12 in Chrome), then navigate to the Network tab. There, you’ll be able to see if any request exceeds the 2-minute threshold.
Best regards,
Łukasz
HI Lukasz,
your hint was extremly helpful!
It is a timeout issue (see attached).
But the good questions is now: "How can I get rid of it?" Where is the problem? Webcon, Server, IIS,...?
Kind regards
Klaus
07.04.2025
15:55
HI Lukasz,
your hint was extremly helpful!
It is a timeout issue (see attached).
But the good questions is now: "How can I get rid of it?" Where is the problem? Webcon, Server, IIS,...?
Kind regards
Klaus
Hi Klaus,
the question is what actions did you define in the OnExit, OnPath and OnEntry triggers?
- Are they creating subworkflows
- Is something maybe creating a deadlock
Did you activate the diagnostic log? I'm not sure that it will return any information, when the executions runs on a timeout.
In most cases you should get a timeout error about to long running executions anyway. Did you increase the setting?
Best regards,
Daniel
09.04.2025
08:37
Hi Klaus,
the question is what actions did you define in the OnExit, OnPath and OnEntry triggers?
- Are they creating subworkflows
- Is something maybe creating a deadlock
Did you activate the diagnostic log? I'm not sure that it will return any information, when the executions runs on a timeout.
In most cases you should get a timeout error about to long running executions anyway. Did you increase the setting?
Best regards,
Daniel
Hi,
You can also set a timeout for the automation execution — this way, you'll be able to easily identify which ones exceed the defined time limit. 😊
Best regards,
Łukasz
