Alex Edelstein

I tried but was not able to reproduce this problem. Exactly what kind of inputs are you providing to the component?

This is a good idea. Someone will need to modify the test. Note that if you're using sfdx you can get around this by removing that file and deploying directly.

most of the stuff in the repo is deployable in packages and so the apex has test coverage. Which one(s) did you spot that weren't deployable that way?

I haven't had time to go deeper...hopefully you're right. alex Alex Edelstein VP Product Management - Automation, Orchestration and Decisioning Salesforce On Mon, Aug 16, 2021 at 3:00 PM fromsteinsfdc...

yes, let's correct.

Fixed in version 1.1 thanks to @AndyHaas https://unofficialsf.com/lookup/

No volunteers so far, @CodeKoz . Any interest?

Thanks for the report! I thought that the current behavior is the desired behavior, to prevent duplicate messages. Can you expand on what the expected behavior should be and why?

Reading a little deeper, it sounds like I'm mixing up messageKey and contactKey

ok, I see the problem now...