Buffer issue

[Former Member]

Hello guys,

I am facing issue becuase of the buffer very frequently.

The agent assignment fails because of this. As soon as I refresh the buffer, it works fine.

Is there a permanent solution for this?

We are in the testing phase in the Quality system. There were no transports which went through for workflow in the past few days. But still the buffer issue came up. NO change was done to the Org.structure also recently.

Can anyone explain and provide the solution?

Thanks,

Ram.

[Former Member]

I wonder about the WF instance log in Transaction SWI1, what is the status of approver step? Error or Ready?

[Former Member]

Hi......The workflow is designed such that it is logically deleted when the approval / reject event happens (even during processing the object outside workflow). So the step is logically deleted.

[suresh_subramanian2]

Hello Ram!

I too faced same issue recently.

Upon raising the event,I couldn't find even the traces at SWEL(trace was switched ON) and to my surprise nothing was in workflow log.I tried SWU_OBUF,PPWFBUF and refreshed the organization settings at SBWP.But, there is no use.

Then I checked the transaction code SM58 where I got answer.The reason was operating system cannot close file dev_PrintTrace.So,check SM58 and also ask your BASIS consultant to increase the buffer size.

Regards,

S.Suresh

[Former Member]

Thanks Suresh.

I will check our Basis team and do accordingly. Will let you know on Saturday(our week starts on SAT).

Thanks again.

Ram.

[Former Member]

Hello,

How does the agent assignment fail? How do you know it's a buffer problem?

So it works after you do SWU_OBUF, but do you have to keep doing it or only once?

(If only once then it's acting more or less as expected - you should always do one after a transport)

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi Rick,

The person(approver) who is supposed to get the work item in his inbox did not get it.

After the buffer refresh (SWU_OBUF), we tried the same and it was working fine and the work item is getting delivered to the correct agent.

To your other question.....The buffer was refreshed after the tranport. It was working. Looks like for the past couple of days the work items are not going to the agent. (This was reported only today!!!!) There were no transports for that workflow in the recent past(after the initial transport) and no change was done to the org.structure also.

Can you tell me whether I need to check anythng else?

Thanks,

Ram.

[Former Member]

Hello,

You wrote:

"After the buffer refresh (SWU_OBUF), we tried the same and it was workng fine"

Do you mean that after SWU_OBUF the workitem arrived? Or that after SWU_OBUF you ran the workflow again and this time it did send the workitem?

I can't think what would cause this. Where is the user reading his emails, in SBWP?

regards

Rick Bakker

Hanabi Technology

[Former Member]

Rick...Thanks for your replies.

We tried the workflow again after the buffer refresh (SWU_OBUF) and it started sending the work items properly after that.

Are there any dangers in refreshing the buffer (SWU_OBUF) in the Production system time and again?

As you said, this kind of behaviour of the system is very surprising.

Is there anyone who is facing similar problem?

Thanks,

Ram.

[Former Member]

Ideally you should not refresh the buffer in Production. You need to sit with the Basis and ask them to resolve the issue.

You have a report that you can schedule but do not do in Prod

RHWFINDEXRESET

Thanks

Arghadip

[Former Member]

Thanks AK.

I am more concerned about the Production environment. How to prevent such buffer issues in Production and if such buffer issue arises in Production, how to handle it.

I checked with the our Basis guys and the question is being put back to me as to what I want them to do/look for specifically.

Any answers for this?

Thanks,

Ram.

[Former Member]

Hello,

Could you answer my questions:

1. Where is the user reading his emails, in SBWP? Or UWL?

2. When you do the buffer refresh, do the existing workflow instances start sending workitems again or do only new workflows send workitems?

If the answer to 2. is existing workflow instances, then what is happening with these workflows in the meantime? Does the workflow log show that it has reached the appropriate step and it has the correct agents, but the users just can't see it in their inboxes?

Doing SWU_OBUF is not a problem in production, it causes a small performance dip (as far as I understand it) but it's certainly not something you want to be doing all the time.

When this is resolved please be sure to post the solution here.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi Rick,

Thanks for your replies.

1. The user sees the work item in SBWP.

2. We could not check whether the existing instances also start sending work items because these objects were completed outside workflow before we refreshed the buffer.

I am using a wait event step in a fork parallell to this dialog step (which should have sent the work item for approval to the agent). The manual completion of the process triggered the event and completed the workflow.

When I come across the same issue again, I will check that and post it here.

Thanks,

Ram.