Workflow Error: "Error when loading the callback component (work item xxx)"

[murtuza_chhatariya]

Hi,

There is a workflow which should be triggered by a disconnect event, this workflow is being used from many years now and having no syntax errors.

But from few days, when I created disconnect event in quality system, workflow gets created but remains in READY state for some time and then goes in ERROR state.

The reason of ERROR status is "Error when loading the callback component (work item xxx)". Also shows that "No Agent Available" in Agent column in SWI1.

I am not getting why suddenly it started going in ERROR state for the same data for which workflow was created last week.

As I am creating workflow in Quality system, so I am sure there is no changes done on template. It looks either with some system enviroment or user authorization!

Thanks,

Murtuza

[Former Member · Accepted solution]

Hi,

First check the whether the administrator is maintained or not through transaction SWDC. If not then please maintain a user as administrator.

Then Check the the configuration in SWU3 whether the configuration is green or not.

Please also check the agent determination process in the workflow design whether the agents are found or not.

Thanks and regards,

SNJY

[murtuza_chhatariya · Accepted solution]

I checked in SWDC, system administator is maintained, there is some number against position.

in SWU3, "Maintain Runtime Environment" is green, the rest of the parameters are red as few of the sub nodes are red

in SWDD, i checked the workflow design is same as in developement and production system.

Also, I am able to create other type of workflows successfully but finding problems in this specific workflow type only.

[murtuza_chhatariya · Accepted solution]

Also, I created the same workflow using different user login, but it still fails, So it is not user specific.

[murtuza_chhatariya · Accepted solution]

When in SWI1, we open Goto > History, it shows the workflow steps and errors, the fourth steps shows error that

"Work item xxx: Object FLOWITEM method EXECUTE cannot be executed"

[Former Member · Accepted solution]

Hello,

What does that fourth step do? Have a close look at the workflow log for any other messages; it sounds like it could be a locking problem (since you said it was READY for a while (how long?) and then went to ERROR).

regards

Rick Bakker

hanabi technology

[murtuza_chhatariya · Accepted solution]

The first step of workflow is very simple container operation. Assigning on value 'X' to one flag.

It remains for around 5 min in READY state and then goes in ERROR state.

How to check what type of locking was there? Can you please provide some steps on it?

[Former Member · Accepted solution]

Hello,

It should be apparent in the workflow log. Look at the technical view of the workflow log, it usually gives you more information. What does the step history of that step say?

regards

Rick Bakker

hanabi technology

[murtuza_chhatariya · Accepted solution]

Its not starting even first step. In Workflow log, there is name of workflow and status is error.

When I click on Details of the name of workflow, below it shows following 2 lines with user names, date and time

(Sub)workflow created

Workflow started

When I click on Graphics, there is event name, and on side Workflow Started (No Agent) and green arrow goes upto first tast (which is container operation) and stopped there.

When I click on the name of workflow in workflow log screen, another screen opens with three tabs Basic data, Activities, Available objects.

Basic data contains nothing but creation date time and status

Activities shows two table controls, first table is Activities (not yet processed), there is one entry in that.

Available objects shows a table contol with two objects.

I check Extras > Technical Data

It shows error as below

Exception 8987

Symbolic Name

Error Type 1

Area SWP

Message 76

Variable 1 xxx

Variable 2

Variable 3

Variable 4

Message Row Error when loading the callback component (wo

[murtuza_chhatariya · Accepted solution]

Solved the issue.

I myself added breakpoints in a task from workflow log which was the cause. I removed it and it started working as before.

But I doubt I created breakpoints in on workflow item, and it not only stopped creating other workflows for my id but from other users as well. This is not accepted.!!

[murtuza_chhatariya]

Hi,

I did set breakpoints in workflow tree and it caused all the workflow going in error. I have mentioned steps where I put breakpoints in above reply. It started working fine as usual when I removed it.

You are getting same error? Did you create anything like breakpoints or something in workflow definition?

Thanks,

Murtuza

[Former Member]

Hi Murtuza,

If a similar error, I have created breakpoint, but I want to verify if any.

Message: Type step expected: Error processing node 0000000XXX índice ParForEach 00000 Exception 8987.

Rgds,

[murtuza_chhatariya]

Workflow stopped being initialized from READY state to STARTED but turning in ERROR status.

There were breakpoints added from administration -> Set Breakpoints in one workflow iteam which caused all the workflow items being created properly by any user!

[Former Member]

Hello,

Thanks for the follow-up. I'd like to know more about this. What sort of breakpoints were these? In ABAP? Where?

regards

Rick Bakker

hanabi technology

[murtuza_chhatariya]

No Breakpoints were not in ABAP code.

See, there is a Task linked to BOR - Method. When you open a workflow item in SWI1, you will see the list of tasks perfomed till date and the task which in process or waiting.

In my case, a worklow had an waiting item, so i clicked on it and it showd me the creation date and start date of task by which date it would start executing.

Now, when we click on Edit > Change, it opens few options on left side like Complete Manually, Set Enqueue lock, Logically Delete etc. There is one more option of Set Breakpoints.

If we open Set Breakpoints option, it will open the full workflow tree having all the tasks as nodes. On side of each tasks, there is gray icon of Breakpoint, when we click any of icon, it turns red (just like we set break point in ABAP Code).

I created 2 breakpoints in one of the task of one of the workitem. But it got hardcoded in all the workflow of that type created by any user. If we open any workflow item of that type, Breakpoints were displayed.

I then went to same position in another workflow item and deleted those.

Thanks,

Murtuza

[Former Member]

Many thanks, I've never seen that option before.

Another item to check if things go wrong.

[Former Member]

Hi Murtuza,

I'm facing the same error. Could you be so kind to share how did you resolve this issue.

Rgds,