You are viewing limited content. For full access, please sign in.

Question

Question

Workflow not running even though starting condition is satisfied

Workflow
Updated November 27, 2019
asked on June 19, 2019

We have a specific workflow/business process that is not running event though the starting condition is being satisfied. As a a result, we are manually starting the workflow.

 

The starting rules are as follows:

I have personally replicated this condition and received the same result (no activity on the document in the repository).

 

While reading other post I tried to view the Subscriber Trace Log, but it does not appear to be any logs in the Workflow Admin Console and/or the folder location for the logs.

 

 

 

 

0 0

Answer

SELECTED ANSWER
replied on June 19, 2019

Thanks, Miruna. As it turns out the Subscriber had lost connection, somehow related to a stop/start cycle we ran the day before to fix a Forms/Workflow connection error we were having. Once I ran a stop/start on the service & subscriber I immediately saw the repository tab in the trace log.  Also, our VAR support team noted that we did not have timeout settings configured so that the subscriber would try to connect again. 

1 0

Replies

replied on June 19, 2019

Does your Subscriber Trace have a tab for the repository you're working with or do you only see the Events tab?

0 0
View 4 previous replies
replied on June 19, 2019

I only see an event tab

0 0
replied on June 19, 2019

Then your Workflow server is not fully configured. You can add a monitored repository either from the Workflow Configuration Manager (only available on the Workflow Server machine) or from the Workflow Administration Console (which can be installed on any machine).

0 0
SELECTED ANSWER
replied on June 19, 2019

Thanks, Miruna. As it turns out the Subscriber had lost connection, somehow related to a stop/start cycle we ran the day before to fix a Forms/Workflow connection error we were having. Once I ran a stop/start on the service & subscriber I immediately saw the repository tab in the trace log.  Also, our VAR support team noted that we did not have timeout settings configured so that the subscriber would try to connect again. 

1 0
replied on November 27, 2019

Hi Miruna,

We have also seen this behavior where  even thought services are running, sometimes workflows do not gets initiated intermittently which then sometimes gets picked up when services are started. during that time screen do not show any trace log and blank as above.

 

is there any fix for this intermittent issue or its default behavior?

 

 

 

0 0
replied on November 27, 2019

The screenshot above shows that there are no monitored repositories. A restart would not fix that issue, it requires configuration.

If you do see the repository tab in the Subscriber Trace, then click on it and see if you see a warning sign on it. It should tell you why the Subscriber can't access the repository.

0 0
replied on November 27, 2019

Hi Miruna - at present issue got resolved with service restart and dont think i had repository tab. but sure if i get error next time. I will capture something to show here.

0 0
replied on November 27, 2019

You can try looking through the Subscriber error log in the Workflow Admin Console. They might give you an indication of what was going on.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...