Custom Action Events arrive in wrong order

When emitting events from a custom action, they arrive in the wrong order;

namespace Microsoft.BotFramework.Composer.CustomAction
{
    public class EventEmitter : Dialog
    {
        [JsonConstructor]
        public EventEmitter([CallerFilePath] string sourceFilePath = "", [CallerLineNumber] int sourceLineNumber = 0)
            : base()
        {
            this.RegisterSourceLocation(sourceFilePath, sourceLineNumber);
        }

        [JsonProperty("$kind")]
        public const string Kind = "EventEmitter";

        public async override Task<DialogTurnResult> BeginDialogAsync(DialogContext dialogContext, object options = null, CancellationToken cancellationToken = default(CancellationToken))
        {
            await dialogContext.EmitEventAsync("Event1", null);
            await dialogContext.EmitEventAsync("Event2", null);

            return await dialogContext.EndDialogAsync();
        }
    }
}

[boydc2014]

At a first glance, looks like not related to the order of event itself, this looks like to be the trigger firing order (ie: Selector) isn’t as ordered as you might see, and that’s by design.

@stevengum @mrivera-ms free feel to assign to me or @Danieladu.

[boydc2014]

@boydc2014 thanks for that. A bit unfortunate it cannot be properly fixed. I now have simply reversed the order and it seems stable. Can you confirm that the order is always just reversed as I could work with that.

At current implementation, it is, and it’s not likely to be changed soon. But i can’t really say it’s guaranteed.

The alternative suggested above, using multiple EmitEvent actions outside this single customized action, is a guaranteed behavior.