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; } } }

Workflow (WFM) never completes

SethHickel

I've used WFM to create a new workflow. I don't seem to be getting any errors but the workflow never completes. It remains stuck in a deploy task. I'm not sure what I am missing - this should be a very simple WF.

Thanks for any help.

Find more posts tagged with

Comments

nipper

OK, is the deploy going ? (likely not) Is this the standard deploy task and not a custom task ? Is there any logging ?

BlueWhale

Looks like something is going wrong with your deploy task ipl. Are you getting the logs until the $task->CallBack function?? If not (probably the case), troubleshoot the script and see at what point its getting struck.

SethHickel

No - the deploy is not going. Looking at logs .. will post

reports1.pdf

SethHickel

Something else that I have read about and am experiencing - the inability to publish from the WFM gui. I have to push from within TeamSite.

vpatel

No - the deploy is not going. With wft's I know where to look for logging because I designate the file to log to - looking for any logging for this WFM ...

WFM doesn't dictate where the logging happens. It seems like your perl script is logging at this location: $iwhome/custom/Administration/logs/deployLowesComLegacySingleServer.log....

SethHickel

Yes - sorry for that log problem.

Interesting - the log is reporting the same error I am getting when attempting to do this with a WFT.

#####Start of log file
### Starting deployLowesComLegacySingleServer.ipl via workflow 2648763

Command -

/Interwoven/OpenDeployNG/bin/iwodcmd start LowesComSingleServerFileListDeploy -k area=Y:/default/main/lowescom/content/STAGING -k filelist=D:/Interwoven/OpenDeployNG/tmp/deploymentlists/2648764.txt 2>&1 1>&2
Result -
Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment LowesComSingleServerFileListDeploy.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Area = not found.

### Finishing deployLowesComLegacySingleServer.ipl for workflow 2648763

vpatel

So this has nothing to do with the WFM...Your deployment is failing with some OD Error. I believe you have another thread open to address that. Please close out this thread if it indeed the other thread and this error are related.

nipper

Oh, you are using the same IPL as with the WFT.

Obviously it is not a WFT/WFM issue, but it has to be in the IPL/deploy combination

SethHickel

A note: I do not want to submit this to TeamSite staging - looking to see if somewhere in this partially borrowed code I am still adding a submit and therefore causing the AREA to be incorrect

nipper

A note: I do not want to submit this to TeamSite staging - looking to see if somewhere in this partially borrowed code I am still adding a submit and therefore causing the AREA to be incorrect

OK, that is an issue that needs to be addressed (but it is not the underlying problem I expect. Your script is deploying from Staging, but the changes are not being pushed to staging, so you are deploying the SOS (same old s...) or you are not sending anything. That should not cause the results you posted.

SethHickel

I'll close this thread and ask that any comments be added to the similar thread "Area = not found"

Thank you.