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.!!