Transactional message routing failed

Avatar

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
androd58052764
Level 2

18-09-2018

Hi,

When I want to send an transactional message with the API and look at the response, I get a status "routingFailed". In the API documentation you get the following explanation:

routingFailed: the routing phase failed - this may occur for example when the type of event specified cannot be found.

This explanation doesn't make me any other wiser. Where do I start looking to fix this?

Kind regards,

Andro Delrue

Accepted Solutions (0)

Answers (4)

Answers (4)

Avatar

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
androd58052764
Level 2

20-09-2018

Hi,

The profile does exist. Here is how my event is set up:

Schermafbeelding 2018-09-20 om 10.11.19.png

Schermafbeelding 2018-09-20 om 10.11.35.png

Schermafbeelding 2018-09-20 om 10.11.49.png

The data I send is something like this:

{

     "email": aa@bb.com

}

The actual email address I use has a profile.
There is nothing wrong with this or am I missing something?

Regards,

Andro

Avatar

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

370 likes

Total Posts

726 posts

Correct reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

370 likes

Total Posts

726 posts

Correct reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Vapsy
Employee

19-09-2018

Hi androd58052764,

You are on ACS and have a transactional event which is linked to Profile schema based on a field, most probably email.

routingFailed means when it tried to connect your event to a template and fetch the personalisation elements something went wrong. In most cases it happens that there is no corresponding profile which the event can link itself to.

Imagin you have defined the event to connect to a profile based on incoming event field cusEmail. The incoming event passes email address abc@mydomain.com as the cusEmail value.

When the system tries to fetch the corresponding Profile, it cannot locate one with the same email address.

Regards,
Vipul

Avatar

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
androd58052764
Level 2

Likes

5 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
androd58052764
Level 2

19-09-2018

Hi,

There is no data in the Message Center, but the weird thing is that when I go to the event I see the transactional message linked to it (see screenshot). Both event and message are published as well.

Schermafbeelding 2018-09-19 om 10.48.05.png

Avatar

Avatar
Boost 5
Employee
Garima_Gakhar
Employee

Likes

44 likes

Total Posts

77 posts

Correct reply

38 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile

Avatar
Boost 5
Employee
Garima_Gakhar
Employee

Likes

44 likes

Total Posts

77 posts

Correct reply

38 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
Garima_Gakhar
Employee

19-09-2018

Hi androd58052764

The 'routingFailed' response is mostly attributed to event not getting mapped to its corresponding template.

To start with, you could first verify does the event template exist on the Message Center Instance, maybe check on it by firing an API Call etc.

If that's positive, then we could investigate further why this error might be coming.