Back in 2022 I see a discussion was raised on this topic:
…and a ticket soon followed. Until this is addressed I noticed a simple CSS addition (with no changes to the existing notification mechanism) can add a simple stacking mechansim. This has it’s limits. i.e. the number of notifications that stack is restricted by the CSS. In this case I only implemented three:
.tc-notification { top: 3rem !important}
.tc-notification:nth-last-child(1) {
top: 3rem !important;
}.tc-notification:nth-last-child(2) {
top: 8rem !important;
}.tc-notification:nth-last-child(3) {
top: 13rem !important;
}

I have been thinking about adding more actions to the button that can override the notification duration setting (for example 10s) then send the notification, followed by setting the value back to its default value. However, a better implementation would be for the notification mechansim to support a duration parameter and/or support a notification duration field in the notification tiddler. However, I might be able to support this in the action list as well.