Need help in a particular scenario of PublishAndWait

[Yemi_Bedu]

Hello,

To really get you some usable answers, lets try to clearly look at the steps you run:

Service Path 1	pub.publish:publishAndWait	Insert to DB (inbound table)	Repeat Start (wait for data in outbound table)	Formulate Document Type	pub.publish:reply (with Document Type)
			Select top 1 from outbound (while no data give error?)
Service Path 2		Insert Notification Trigger	Some Operation	Insert to Db (outbound table)

Is this right? So there are the questions on what is in the outbound table after the first call. Because if there data in the outbound table is not removed, maybe the same data is being returned the second time (from the first call) and that is being sent in the reply. That would be why your call in waiting, it never gets the proper document back (first doc for second call).

So you would then notice the phenomenon of deleting a document in the outbound table would allow one more iteration of your service to go through. I think you need to have some like the following to help you:

Service Path 1	pub.publish:publishAndWait	Insert to DB (with ID)(inbound table)	Repeat Start (wait for data in outbound table)	Formulate Document Type	Delete from outbound table where ID = selectedID	pub.publish:reply (with Document Type)
			Select top 1 ID from outbound table [store in selectedID](while no data give error?)
Service Path 2		Insert Notification Trigger	Some Operation	Insert to Db (outbound table)

This should allow you to get the effect you want. Thank you. Good day.

Yemi Bedu

[Yemi_Bedu]

Hello,

You should just be doing your select for the record that has the same ID (plus option conditions) you saved in the inbound table:

Service Path 1	publishAndWait	-->	-->	-->	-->	-->	-->	Some Op
Service Path 2	Trig	Insert into inTable(ID, other fields) Values (%currentID%, other values)	-->	-->	Repeat Start (wait for data in outbound table)	Form Doc Type	update outTable set picked = 'true' where ID = currentID	reply (with Document Type)
					Select top 1 * from outTable where ID = currentID and picked = 'false' (while no data give error?)
Service Path 3		Insert Notif Trig	Some Op (obtain newID)	Insert into outTable (ID, other fields, picked) Values (%newID%, other values, false)

You don’t have to filter on those records that are picked already, since I would hope that the ID used is a new one every time. I would think that it should not hurt to have this condition in the clause. It would help to eliminate a similar issue based on the data type used to store this ID, where it may hit some upper limit. This all should allow you to keep track of those records that are freshly set and those which are already picked. Good day.

Yemi Bedu

[Guest]

Got it !! Thank you for all your support !!!