how to troubleshoot callback calls

The first task in my workflow is the externaltask. I have noticed that the workflow transition to the next task even before the code tries to make a callback (to the workflow engine) within the external perl script.

I have tested furher:
A task transitioned to the next one happens, even though all callbacks were commented out.

I put extra logs into my external perl script and quite early in that script, as soon as the external script log file was initialized the task state was checked:
$task->GetState()
The task state was: inactivated
This is really strange, since the external script didn't reach main() subroutine point yet.

What would the best way to test and see how/when the workflow transition to the next task and what/who triggers that?

Find more posts tagged with

Comments

chandraiw

is the timeout element set for that external task?

boskovuk

is the timeout element set for that external task?

No, timeout element is not used at all.

I have attached the details of the external task (copy/paste from WFT file).

chandraiw

iwgetwfobj job_id should give you the task activation/inactivation /callback event times (seconds from 1970)

Adam Stoller

No, timeout element is not used at all.

I have attached the details of the external task (copy/paste from WFT file).

Can you post

It's possible that this is more of a logic-issue than a product-issue, but it's difficult to say without seeing more of the context.If you can simplify either/both and still replicate the problem - please post the simplified versions rather than the full versions (better all around that way).

boskovuk

Can you post
the code for the externaltask script
the complete WFT
It's possible that this is more of a logic-issue than a product-issue, but it's difficult to say without seeing more of the context.

If you can simplify either/both and still replicate the problem - please post the simplified versions rather than the full versions (better all around that way).

The external script is pretty simple (if you don't analyze the debug/troubleshoot code). I have attached the externaltask script and complete WFT.

In addition, to reply back to chandraiw suggestion, attached is the outcome of this command:
iwgetwfobj 6766

chandraiw

The external script is pretty simple (if you don't analyze the debug/troubleshoot code). I have attached the externaltask script and complete WFT.

In addition, to reply back to chandraiw suggestion, attached is the outcome of this command:
iwgetwfobj 6766

might be a bug, but you've got 'start' attribute set to 'true' for more than one task

boskovuk

might be a bug, but you've got 'start' attribute set to 'true' for more than one task

bingo.
That's it. I cleared this attribute for "Start MetaTagger" task and at finally I see the callback mechanism working. Since all callbacks are commented out, the task is in expected state (active).

thanks a lot ... Smiley Happy

Adam Stoller

bingo.
That's it. I cleared this attribute for "Start MetaTagger" task and at finally I see the callback mechanism working. Since all callbacks are commented out, the task is in expected state (active).

thanks a lot ...

Glad you (via chandraiw) got it fixed - that was the kind of logic error I expected would be found.