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

Prod environment

spayal

In a prod environment, I have publish content workflow. One user was using this wf till 9 pm to publish content and after that it gives an error "error in wf at line 76". What can this be due to ?

If I want to check whether this wf is working for me or not, how to check that ? If I use this wf to publish content in prod environment and test it, wont the content be updated on the website ? If yes, then how to check the wf is working for me or not ?

Pls answer ASAP.

Find more posts tagged with

Comments

Faizi

In a prod environment, I have publish content workflow. One user was using this wf till 9 pm to publish content and after that it gives an error "error in wf at line 76". What can this be due to ?

If I want to check whether this wf is working for me or not, how to check that ? If I use this wf to publish content in prod environment and test it, wont the content be updated on the website ? If yes, then how to check the wf is working for me or not ?

Pls answer ASAP.

Are you talking about "Publish Livesite Content" workflow?

Also check the cssdk.log and servlet_out.log file for what exactly the exception occured?

sumitk

If I want to check whether this wf is working for me or not, how to check that ? If I use this wf to publish content in prod environment and test it, wont the content be updated on the website ? If yes, then how to check the wf is working for me or not ?

It seems that you yourself is not aware of your existing workflow structure. Before running the workflow, make sure that you fully aware of the workflow. Go through WFT file of the workflow. Check whether anyone has changed the WFT file. This is the probable reason of the error that you are getting right now.

Also, you can always use iw_debug mode so that you can get xml format of you workflow job. If you enable debug mode in you workflow, the job will not be initiated but you can verify the well formed xml of the WFT.

Hope this helps.

Cheers,
Sumit

shahzamaj

Sorry , wrong message

spayal

how to use iw_debug mode ?
Can you pls tell me how to debug this wft file ?

thanks

nipper

set that to true (either hard coded in the WFT or in the instanciation screen) and then it will create an XML file that you can view to see what the errors are. The XML file created is defined in the WFT.

spayal

You said set iw_deg to true in wft file.
where do I set iw_debug to true ? I mean at what place in wft file ?

thanks

sandy123

You said set iw_deg to true in wft file.
where do I set iw_debug to true ? I mean at what place in wft file ?

thanks

Please read the Workflow developer's Guide. You will find all these details very easily in the pdf.
If you still face issues then post your code here. We will be help you.

Thanks,
Sandy

spayal

I did check some of my wft files. iw_debug mode is on.
So now when I run a job, that job will not be instantiated ?
Only xml file will be formed ? where will this xml file be formed ? How can
I access tghis file ?

thanks

Untitled.png

sumitk

So now when I run a job, that job will not be instantiated ?
Only xml file will be formed ? where will this xml file be formed ? How can
I access tghis file ?

When you run the job, the job will not be created. You will see the JOB xml file in the browser. You can go through that file for debugging.

Cheers,

Sumit