Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
3 replies Latest Post - ‏2012-11-21T00:23:37Z by KaranBal
SystemAdmin
SystemAdmin
648 Posts
ACCEPTED ANSWER

Pinned topic Item going from success into fixit, but should never happen

‏2012-10-11T12:10:58Z |
Hi all,

I have a strange bug in a workflow.

The workflow processes an item and there is a step where I can modify it and then click on 'Done'.
This should just save the item and move it to success step and it does. But then, a few seconds later it appears in the fixit. The fixit step is not configured in any way in the workflow and the item should never enter that step. How is it possible for the item, after being process successfully, to appear in that step.

Regards,
Han van den Heuvel
Updated on 2012-11-21T00:23:37Z at 2012-11-21T00:23:37Z by KaranBal
  • SystemAdmin
    SystemAdmin
    648 Posts
    ACCEPTED ANSWER

    Re: Item going from success into fixit, but should never happen

    ‏2012-10-11T12:20:57Z  in response to SystemAdmin
    Hi,

    it is a special build-in step like SUCCESS and INITIAL. If some issue happens during Check-In, for example, an item is transfered into Fixit step. Check logs, the item unique constrains and etc
  • SystemAdmin
    SystemAdmin
    648 Posts
    ACCEPTED ANSWER

    Re: Item going from success into fixit, but should never happen

    ‏2012-11-12T14:14:53Z  in response to SystemAdmin
    After long debugging we were able to figure out what was wrong. Still the question remains why no exception was thrown. A recursive relationship lookup went wrong on like the 3rd item since some value was not correctly set.
    • KaranBal
      KaranBal
      108 Posts
      ACCEPTED ANSWER

      Re: Item going from success into fixit, but should never happen

      ‏2012-11-21T00:23:37Z  in response to SystemAdmin
      If the error i.e. recursive lookup requirement was a part of your custom script, then it is not necessary that an error will be thrown. If an attribute has a value which isn't allowed, then an error will be thrown in the UI e.g. float value when the type of attribute was integer or a required attribute not filled. If instead, the error occurred in post save or post processing, then often the item ends up in the fixit step.
      You may check the $TOP/logs for an error entry.