latest posts

Hello,

we are using the API to create workflow instances by another system. We are also checking if this workflow has already been created.

Now to the problem:
Unfortunately we are not able to access the archived instances with api-call and check for existing workflows: api/data/v5.0/db/{{dbid}}/applications/{{applicationid}}/search?search=xxxx:xxxx

if the workflow instance is not yet archived we are able to access it.

Is there a way to access archived workflows via API?

Thanks a lot!

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 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,

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,
Maybe check logs in table Content Database

SELECT *
FROM [dbo].[WFActionExecutions]
where LOG_WFDID = <Your WEBCOND ID>
order by 1 desc

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,
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 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?

Ok, now it's clear. I knew about "Move workflow (sql)" and "Update related workflow instance" actions but this "Change Field Value" confused me :) Thank you.

Hi Arek,

the action can only be used in combination with automation parameters in a cyclical action.

The cyclical action itself runs without a context.

You can use either the "Move workflow (sql)" action and add the necessary actions to the path of the workflow or use the "Update related workflow instance" action. The later one is the same as hitting the save button.

Best regards,
Daniel