Timeout Issue: The timeout period is only defined relative to the time of the entry to the node, meaning only a definition "wait for x days/ hours" is possible.

Problem Case Example Journey: Event is taking Place on September 30th

On September 1 invitation is sent. The Node has a timeout defined of 20 Days with the check, if the event registration was clicked during that time. If the link is visited a registration confirmation message is sent to the invitee. If the link is not visited within 20 days, the invitee exits the trigger node on the negative path, receiving a reminder for the event registration.

On September 15th, 10 additional Contacts are injected Manually into the Journey by editing the Segment.
5 of them don't ever click the registration link but since the trigger timeout is relative to the entry time into the Trigger Node, They will exit the Node on the negative path on October 5 Receiving a reminder to register for an event that has already taken place.

This is the reason why the Trigger node needs the option of defining an Timeout that is based on an absolute deadline like "Wait until 20th of September". With this it does not matter if contacts are added at a later date as long as it is before the absolute deadline. Even if the are added after September 20th, they should immediately leave the node upon arrival on the negative path.

Adding a timer in front of the trigger as suggested does not solve this issue. Problem is, lets say
we add a timer that waits until September 20th before the contacts may even enter the trigger node where the split happens. Contacts that have clicked the Registration Link on September 1 will have to wait until
September 20th to receive the registration confirmation which is not an acceptable solution.

Please vote for the option. Other tools on the market are able to handle these standards and this is supposed to be the premium choice.