More problems – now with SEND action

[Anonymous]

I’m struggling these last couple of days.

I have used the SEND action before with no problems, but this time I’m having a hard time with it.

I am putting my SEND at the end of an iterate, with a SUPPRESS after the iterate (to not duplicate a message).  If I Iterate twice, I get both messages crammed together into one, but nothing gets saved to my outbound saved file.  It’s like the message isn’t completing on SEND.

Any ideas on this one?

Topic

[Anonymous]

I just built a quick little test interface and sent the inbound data to it.  It routed and translated exactly as I expected it to.

Is this maybe a bug in th 5.2 xlt tester?

[Anonymous]

Just wanted to add a comment on SEND.

When the engine is processing a route full of many route details and one route detail fails, then the engine dumps all the route details.  This protects the system from sending out messages that might have errors.  However, when you use SEND in a translation then the sent message persists even if there is an error in another route detail.  If this is the effect that you want then you’ll need to push the send message tranlation detail up to the top of the list of details to prevent it from not being executed.

If this isn’t the effect that you want then use CONTINUE instead of SEND.

And you’re correct, the test tool isn’t spacing between messages 😐

[Author]

Replies