Workflow Object Issues

We have been having some problems in one of our TeamSite instances that I thought might be related to an issue with the workflow store.

To check, I built a script that pulls everything generated by iwgetwfobj into a file and then calls all of the objects listed therein, checking for validity of the workflows.

Three workflow ids returned an error :

Workflow object 5403584 does not exist.
ID 5403584 is invalid
Workflow object 5409089 does not exist.
ID 5409089 is invalid
Workflow object 5916654 does not exist.
ID 5916654 is invalid

Although I know that I can remove them (or, I think I can...), I first wanted to look into each one to determine what caused the problem. Is this possible? I am unable to pull them up with the clt 'iwgetwfobj'.

Any suggestions?

(synopsis : a straight iwgetwfobj call shows three workflows that do not exist when you call them individually)

Find more posts tagged with

Comments

Adam Stoller

We have been having some problems in one of our TeamSite instances that I thought might be related to an issue with the workflow store.

To check, I built a script that pulls everything generated by iwgetwfobj into a file and then calls all of the objects listed therein, checking for validity of the workflows.

Three workflow ids returned an error :

Workflow object 5403584 does not exist.
ID 5403584 is invalid
Workflow object 5409089 does not exist.
ID 5409089 is invalid
Workflow object 5916654 does not exist.
ID 5916654 is invalid

Although I know that I can remove them (or, I think I can...), I first wanted to look into each one to determine what caused the problem. Is this possible? I am unable to pull them up with the clt 'iwgetwfobj'.

Any suggestions?

(synopsis : a straight iwgetwfobj call shows three workflows that do not exist when you call them individually)

I suggest you contact IWOV Support - and do not muck around with the workflow store until/unless directed to by them.

If I recall correctly - it's generally and all-or-nothing issue - either you remove the entire workflow store or you leave things the way they are - this is the reason you should talk to support first.

jajtiii

All that's been done. I am doing this after a support ticket was submitted and one of the options (of 2) was to get the (corrupt) jobs, if they existed, and remove them.

But, thanks for taking the time to throw your two cents in regarding the premise of my question.

Regardless, I am interested in delving into this a bit deeper. I am currently looking at some perl modules to see what they can do, but if someone has another method or option to getting info on these fouled jobs, I'd love to have a look.

thanks,

jt