Dispatcher Goes into Infinite loop in - Re Framework , need help

I have a dispatcher with 3 queue items to push
dispatcher Activity is set inside Process transaction state and I have deleted GEt transaction item state from re framework

now when i try to run my dispatcer but it keeps on running despite giving an error in my logs , it wont stop after exceution phase as well

image


can someone tell what configuration mistake i have done

1 Like

Hi @samantha_shah . Can you check the condition in transitions T1 and System exception?

1 Like

HI @devik

here is the condition

1 Like

For the System exception transition from Process transaction state to Init state, the condition is SystemException IsNot Nothing to force it back to init on exception. For T1, to end process on successful completion of Process, change the condition to SystemException Is Nothing. Hope this helps…

1 Like

Hi @devik

I tried setting the condition and gave wrong data table entry, wrong column name

it still goes in loop

should I put one more condition ?? here or just modify the t1 as I did ??
image

image

1 Like

Hi @devik

I tried setting the condition and gave wrong data table entry, wrong column name

it still goes in loop

should I put one more condition ?? here or just modify the t1 as I did ??

image

1 Like

REFramework is way overkill for a dispatcher. It’s more intended to be used as a performer, but I don’t even like it for that. I suggest you save yourself the hassle and just write a dispatcher from scratch. Much simpler.

1 Like

Hi @postwick

client wants in re framework

1 Like

If you don’t have to loop back to init incase of exception, then you just need to have only 1 transition from process transaction to end process with condition True. The purpose of System exception transition is retry from init state incase of exception…

2 Likes

I would respectfully and politely explain to the client why that’s a bad idea. Explain to them what a black box is.

1 Like

We use REFramework as dispatcher and it works very well. We route all errors and success to end process. Never had an infinite loop. I would not consider it an overkill, else we would be required to recreate the proper error handling and config management (dev,q,prod).

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.