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

Removing bad workflow

System

I was recieving an "invalid argument" error on one of my workflows when I tried to click on it from the workflow/jobs in CCPRO. There weren't any tasks associated with it anymore, somehow it got corrupted.

Here was my solution-

Do this at your own risk. Make a backup of your workflow folder before doing any of this. My job didn't have a description for some reason (part of the corruption) so I used "iwsetjobdescription" to add a unique description to the job. I then went into iw-store\workflow and did a search on the files for my unique word (in this case I used bubbles). When I found the file that the word was in I was then able to go into that folder and delete the two workflow files (f6c and f6c_ in my case). I then went back into Teamsite and the job was gone.

I'm sure it's not supported, but it sure beats having to tell your users that in order to remove a bad workflow you need to delete the entire workflow folder and have them recreate their jobs.

Notes - I previousely had tried to end the job and to use iwrmjob, but both of these made Teamsite drop to it's knees to the point that I had to kill the service.

Find more posts tagged with

Comments

Migrateduser

Did you run iwfsck to check if there are any errors in the store before and after you deleted the files from the workflow store.

I do agreed that deleting the workflow store and recreating the store is not the best way to delete couple of bad workflows.

Migrateduser

Yes, the store was error free. (I just performed an iwmigrate this weekend to replace my original corrupted backing store) I copied over my workflow folder over to my new store and it worked fine except for that one workflow.

Adam Stoller

Did you run iwfsck to check if there are any errors in the store before and after you deleted the files from the workflow store.

I do agreed that deleting the workflow store and recreating the store is not the best way to delete couple of bad workflows.

Unless something has changed recently - iwfsck does not perform any consistancy checks on the workflow store - only the content store(s).

Crosstab Question.doc

Migrateduser

Unless something has changed recently - iwfsck does not perform any consistancy checks on the workflow store - only the content store(s).

I was under the impression that iwfsck can be used for all the stores including the workflow store, but I might be wrong.

Is there any other utility that used to check for errors in the workflow store?

Thanks for correcting me about iwfsck CLT usage.

Adam Stoller

I was under the impression that iwfsck can be used for all the stores including the workflow store, but I might be wrong.

Is there any other utility that used to check for errors in the workflow store?

Thanks for correcting me about iwfsck CLT usage.

I think a request for a utility (or enhancement to iwfsck) to check the workflow store was filed a number of years ago - though I don't know the number. You can always contact Support to see about this and then report back with the number (old or new) and invite customers to add their backing to making it happen...