Alternate exit in real time journey with "registration cancelled" trigger throws error message

(1) Share

Report

Posted on by jaa

Hi everyone
I have been using the 'Cancelled Registration' trigger as an alternate exit for a real-time journey for some time now, but all of a sudden when I want to use it, I get the same error message saying 'The selected trigger is not supported for the current data source'. Does anyone know what this could be? Thanks a lot!

I have the same question (0)

All responses (5)

Answers (3)

Verified answer

Leah Ju Microsoft Employee on at

Like (0)

Report

Hi Partner,

Suddenly like this? Possibly from a version update?

Customer Insights - Journeys offers three types of triggers in the triggers catalog: custom triggers, interaction triggers, and business triggers.

Through my test:

1.In the 1.1.32267.116 version

If we populate interaction triggers or part of business triggers(Customer Insights - Journeys event check-in created;Customer Insights - Journeys event registration created;Customer Insights - Journeys event registration canceled;Customer Insights - Journeys form submitted) in the 'Alternate exits', the error will appear.

--For example:

2.In the 1.1.32267.120 version, it's ok.

As the following documentation said, try to update to latest version:

https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/setup#install-uninstall-or-update-customer-insights

I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No
jwcpc 274 on at

Like (0)

Report

Yep, had the same issue here. Using a Event Registration trigger for my Journey start, and a Registration cancelled for my exit. The journeys were published few weeks back with no errors, now the journeys get the same error:

'The selected trigger is not supported for the current data source'

Have you had any update on this? I'm not sure if the exits for the journeys previously published are working or not. Also means journey exits are rendered useless as it also won't allow you to use the same trigger type for start and exit.

Was this reply helpful? Yes No
Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report

Hi jwcpc,

It doesn't matter what kind of trigger is used, it's just a bug caused by a version update.

Everything works fine for me after updating the version.
I tested it in the latest version(1.1.32267.120) and everything works fine:

When i use the 1.1.32267.116 version, same error with you:

So you can try to update to latest version:

I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No
Verified answer

PaulineKolde 732 Moderator on at

Like (0)

Report

Hi Janine,

this is a known issue. I build a workaround with dataverse triggers. But it is fixed now by MS. When updating to the latest version you will be able to use the default triggers again.

Best

Pauline

Was this reply helpful? Yes No
Verified answer

jaa 76 on at

Like (0)

Report

It worked with the Version Update, thank you all!

Was this reply helpful? Yes No