Workflow debugging

Hi,

When i click on new job and try to instantiate a workflow it hangs, this behavior occurs at random sometimes the same piece of code instantiates the a new job and some times it does not.

What can be the probable reason? It does not create any logs when it hangs.

Teamsite Version 6.5 sp2
Windows environment.

Thanks in advance.
Ashish

Find more posts tagged with

Comments

Adam Stoller

Hi,

When i click on new job and try to instantiate a workflow it hangs, this behavior occurs at random sometimes the same piece of code instantiates the a new job and some times it does not.

What can be the probable reason? It does not create any logs when it hangs.

Teamsite Version 6.5 sp2
Windows environment.

Thanks in advance.
Ashish

Does it hang before, or after, the instantiation screen?
Does it happen with OOTB workflows or only custom workflows?

ashish_7800

It hangs on the Workflow form which user fills in and click done to instantiate new form.
It happens mostly when during development there is some issue and it stops working, but inspite of reverting the code (which was working earlier ) it still hangs.

Where do i need to look for possible issues ?

kaalraa

Hi,
When i click on new job and try to instantiate a workflow it hangs, this behavior occurs at random sometimes the same piece of code instantiates the a new job and some times it does not.
What can be the probable reason? It does not create any logs when it hangs.
Teamsite Version 6.5 sp2
Windows environment.
Thanks in advance.
Ashish

Could you please elaborate as what your workflow does within template_script? It might be doing some functionality which fails (sometimes) and due to which it hangs up.

ashish_7800

My workflow is for search and replace.

Now i am trying to update that to take care of new functionality. Instead of a default search at root folder i want to initiate my search from the folder where the user has started his workflow ( with/without files that he has selected ).
For this i am trying to make use of __ELEM__('iw_file') to get the number of files attached as well as the location. and __VALUE__('iw_file') to get the list of files attached.

In case something does not works i revert the code to the last working one but still it hangs and all of a sudden starts working.

Thanks
Ashish

Migrateduser

If you are starting the workflow from "Workflow" tab using "Action->New Job" you will not be passed the 'iw_file' attribute.

kaalraa

My workflow is for search and replace.

Now i am trying to update that to take care of new functionality. Instead of a default search at root folder i want to initiate my search from the folder where the user has started his workflow ( with/without files that he has selected ).
For this i am trying to make use of __ELEM__('iw_file') to get the number of files attached as well as the location. and __VALUE__('iw_file') to get the list of files attached.

In case something does not works i revert the code to the last working one but still it hangs and all of a sudden starts working.

Thanks
Ashish

Are you cross-verifing the values being fetched from iw-file element. What is the catch, try exception clause you are using to handle the same, if there is no file being attached to the job.

ashish_7800

I got the error it was due to the text editor I was using, which was adding special character when i used to copy the .wft file from my desktop machine to windows teamsite server, which made the file non-readable by the workflow engine.

I changed and editor and it started working.

Thank you everyone for your help.

Ashish

APIs.zip