AutoWear Problem getting AutoWear Tasker Profile to trigger

I have created an AutoWear Command Event profile in Tasker on the &APPOPENEDCOMMUTE& event. This was successfully triggered once but now I can't get it to trigger again. The toast appears indicating that the command was received but the profile never triggers.
I have enabled logging in Tasker and can send the full log if necessary. These are a couple of events from the log file which seem relevant:

Code (Text):

14-04-2019 M: 09.14.55#M: received UNSATISFIED from plugin com.joaomgcd.autowear\n***\n*!&$*;com.joaomgcd.autowear.activity.ActivityConfigCommand / AutoWear Command Event: &APPOPENEDCOMMUTE&

14-04-2019 : 09.15.15#:     com.twofortyfouram.locale.intent.extra.ACTIVITY / com.joaomgcd.autoappshub.activity.ActivityConfigCommand (java.lang.String)
14-04-2019 : 09.15.15#:     net.dinglisch.android.tasker.extras.PASS_THROUGH_DATA (Bundle)
14-04-2019 : 09.15.15#:         com.joaomgcd.common.EXTRA_JSON_PAYLOAD / {"mc":{"message":"\u0026APPOPENEDCOMMUTE\u0026"},"text":"\u0026APPOPENEDCOMMUTE\u0026"} (java.lang.String)
14-04-2019 : 09.15.15#:         net.dinglisch.android.tasker.MESSAGE_ID / 1288534037 (java.lang.Integer)
14-04-2019 : 09.15.15#:     eventType / 9982 (java.lang.Integer)
14-04-2019 M: 09.15.15#M: queryPluginsWithEditClass: com.joaomgcd.autoappshub.activity.ActivityConfigCommand
14-04-2019 Log: 09.15.15#Log: pass through
14-04-2019 : 09.15.15#:     com.joaomgcd.common.EXTRA_JSON_PAYLOAD / {"mc":{"message":"\u0026APPOPENEDCOMMUTE\u0026"},"text":"\u0026APPOPENEDCOMMUTE\u0026"} (java.lang.String)
14-04-2019 : 09.15.15#:     net.dinglisch.android.tasker.MESSAGE_ID / 1288534037 (java.lang.Integer)
14-04-2019 M: 09.15.15#M: qpwec: no events with code 18927444, hope plugin shuts down soon...
 

Any ideas why the profile is not triggering?

Edit: I have now found that this actually works if I use an AutoApps profile with a command filter of &APPOPENEDCOMMUTE& but not the AutoWear one. Strange that one works and the other doesn't. I have already tried uninstalling and reinstalling AutoWear.

 

No, the profile wasn't disabled. Although it is actually disabled now, since I have switched to using an AutoApps profile for the same command which seems to be working consistently. I just testing disabling the AutoApps profile and re-enabling the AutoWear one but it still didn't work, so I'll stick with using the AutoApps one for now.