nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to debug workflow when debug option is on

KhushiAgrawal

Hi,

I am facing the issue while accessing workflow.

So i made debug mode on as a result I can see the yellow n green window but i am not sure how I can see the error in that window. yes we can see the error in the logs as well but just want to know how to do debugging in that window?

Find more posts tagged with

Comments

Rick Poulin

The yellow and green boxes show you the jobspec and model right before it's submitted to the workflow engine for instantiation. If your problem is an instantiation one, you want to look in these boxes for what might cause the problem.

For example, the most common problem is that your workflow won't instantiate because a task owner or group specified in the workflow doesn't have access to the current workarea. So you'd look through the computed jobspec at all task owners/groups and confirm that each always has access.

KhushiAgrawal

Thanks for Sharing the info. I understand now.

The user is TS master.

users belongs to iwEverone group.

I feel if user is TS master it should have access to use workflow for all the branches. Please guide me on this what can be done in order to resolve this issue.

Rick Poulin

You misunderstand my point. The user that launches the workflow is only one piece of the puzzle.

Let's say, later on in the workflow, you have a group task, shared with a group containing users Jimmy and Bob. Well if Jimmy and Bob don't have access to the workarea, then your workflow will fail to initialize.

This is the most common reason for a failure to initialize, but there are others. The error message usually gives you some indication of what to look for.

KhushiAgrawal

Ok. So You want me check the permission of the users which is involved in the some group or individual task.

But I have done the iwidmap for all the users so all the permission should be same as old right?

Adam Stoller

The original question / title of the thread is "How to debug workflow when debug option is on" - the issue you would be debugging there usually has to do with failures to instantiate. Since you never actually stated what it was you were trying to do - it's difficult for us to guide you on how to do it.

If the workflow fails to instantiate, but you can get to the yellow/green window - there should be some indication as to "why" it failed to instantiate - i.e. an error message - either displayed in a pop-up window or found in one of the various log files (e.g.: attempt to run the workflow and then look for any logfile that just got updated) - I'd look in IWHOME/local/logs, IWHOME/local/logs/iwui, and ApplicationContainer/server/default/log).

If that's the case - please let us know what the actual error message is / are.

If the workflow fails to instantiate - again, you need to provide whatever error messages you get - this is usually an indication of broken code in the WFT or WFM (which is it? You didn't say)

If the workflow instantiates (with debug option disabled) - but there's a problem with it - we would need to know a lot more about where / how it is "failing" - the yellow / green windows won't help you very much here.

So - rather than continuing to jump to conclusions - perhaps you can provide more details about the issue to help us help you.

KhushiAgrawal

Hi,

Please have a look into the attached files.

Please let me know if any other details needed.

thank you so much for your valuable waiting for your reply.

KhushiAgrawal

Please find the error.log filse also.

nipper

The last 2 tasks in the WF have a blank name as well as blank tasks listed on success.

The problem with using the default submit WF is that it builds the XML on its own and gets messed up if you configure it wrong.

KhushiAgrawal

Many thanks Andy for your valuable time.

so mean to say the problem is with : below two task?

<externaltask name="" owner="code1\310178050" description="" lock="f">
        <areavpath v="/default/main/publicweb_healthcare/global/main/webdevelopment/WORKAREA/w-main"/>
        <successors>
            <successorset description="Finish">
                <succ v=""/>
            </successorset>
        </successors>
        <command v="D:\Interwoven\TeamSite/iw-perl/bin/iwperl \Interwoven\TeamSite/local/config/wft/solutions/iw_solution_email.ipl -t &quot;&quot; -t &quot;&quot;"/>
        <timeout v="+000001">
            <succ v=""/>
        </timeout>
        <activation>
            <pred v=""/>
        </activation>
        <variables>
            <variable key="iw_mailbody_pt" value="no_deploy_iwmailbody.tpl"/>
            <variable key="iw_mailheader_pt" value="no_deploy_iwmailheader.tpl"/>
        </variables>
    </externaltask>

    <usertask name="" owner="Everyone" description="">
        <areavpath v="/default/main/publicweb_healthcare/global/main/webdevelopment/WORKAREA/w-main"/>
        <successors>
            <successorset description="Retry">
                <succ v=""/>
            </successorset>
            <successorset description="Cancel Job">
                <succ v="End"/>
            </successorset>
        </successors>
        <activation>
            <pred v=""/>
        </activation>
    </usertask>

Adam Stoller

KhushiAgrawal wrote:

Many thanks Andy for your valuable time.

so mean to say the problem is with : below two task?

<externaltask name="" owner="code1\310178050" description="" lock="f">
        <areavpath v="..."/>
        <successors>
            <successorset description="Finish">
                <succ v=""/>
            </successorset>
        </successors>
        <command v="..."/>
        <timeout v="...">
            <succ v=""/>
        </timeout>
        <activation>
            <pred v=""/>
        </activation>
        <variables>
            ...
        </variables>
    </externaltask>

    <usertask name="" owner="Everyone" description="">
        <areavpath v="..."/>
        <successors>
            <successorset description="Retry">
                <succ v=""/>
            </successorset>
            <successorset description="Cancel Job">
                <succ v="End"/>
            </successorset>
        </successors>
        <activation>
            <pred v=""/>
        </activation>
    </usertask>

Absolutely! - you cannot have a task with no name, nor can you have 'succ' or 'pred' elements with no ('v') names.

If you don't understand the configuration of the OOTB workflows, you might be better off creating your own from scratch using the [Legacy] Workflow Developer's Guide to help you. There's a lot of extra stuff going on in the OOTB "configurable" workflows that you probably don't need and it just adds clutter and confusion to the process of doing the development.

Note - if you get the task name's fixed, chances are the 'succ' and 'pred' elements will also be fixed (i.e.: don't worry about those until you either fix, or remove, the tasks with no names)

KhushiAgrawal

Hi,

As i understood from the attached code we have all the task with name and success task. And in the log I am not getting any error msg also Smiley Sad

nipper

If you are not getting an error message, then what is happening ? Say no to debug and run it.

KhushiAgrawal

Hi,

Thanks for looking into this.

I have made the debug ode off and was trying to put logger in wft file but there is no such error i got it passing trough all th functions.

I am attaching the wft, workflow log and error screenshot. Since we dont have any one in the project to work on this and I am not getting what is the issue so could you please guide me on this ?

Many thanks Smiley Happy

KhushiAgrawal

Hi,

Now I am not getting that successer empty error.

Now its giving me User Everyone has not role.(Screen shot attached)

Can you please guide me how its setting that in the xml ?

Adam Stoller

What this means is that somehow, one or more of the tasks is owned by "Everyone" - which is a group not a user - and that the group "Everyone" has not been assigned any role on the branch where you are trying to instantiate the workflow - nor should it be.

My guess is that the workarea in which you are working is, incorrectly, owned by "Everyone" and that one of the tasks (likely Submit) is owned by the "areaowner" - and thus you are getting this error.

KhushiAgrawal

Yes you are right, Now I have given right permission so its working fine. Thank you soo much for your help in this.

The another issue I am facing is the content is not getting deployed on one particular node(server) i am getting below error message:

ENG: End of deployment config file[D:\Interwoven\OpenDeployNG\conf\PublicWeb-Sandbox-DoDeletes.xml]

ENG: ***ERROR - Unable to resolve Node name usdanrmmd1ms535. Check your node name.

ENG: ***ERROR - Failed to start deployment.

I have changed the odresv.xml on target servre. Could you please let me know what this error message is saying?

Kalam

Hi ,

Do you have the usdanrmmd1ms535 in the odnodes.xml file? If not please add this in the odnodes.xml and try to deploy again.

Thanks
Kalam

Adam Stoller

KhushiAgrawal wrote:

ENG: ***ERROR - Unable to resolve Node name usdanrmmd1ms535. Check your node name.

This sounds like it's an issue with not having the node 'usdanrmmd1ms535' defined in the ODHOME/etc/odnodes.xml file on the sending (Base) server.

If that node is the sending (Base) server, then it would be indicative of the Receiver not having that node defined in the AllowedHosts sections of the ODHOME/etc/odrcvr.xml.