AutoVoice AutoVoice action error 404 when setting context

I recently migrated my tasker and autovoice setup from one phone to another. Unfortunately, during that process one thing stopped working. I have an intent that is followed by another intent. They share context. After the first action is detected by a tasker profile, the task uses the AutoVoice Natural Language Context action to set the context parameters for the following intent. This used to work brilliant. However, since I migrated to my new phone, the action results in AutoVoice action error java.io.IOException: Error 404.

Any ideas what could be wrong?

 

Thanks! That fixed the original error. However, now it's impossible to set input/output contexts for natural language command. Again, error 404.

 

No, initially, the problem was with setting the context values using the tasker action. Now, instead, the problem is with defining contexts in using AutoVoice->Natural Language->Commands->Command->Input Contexts/Output Contexts.

 

Thanks, no error when setting context, but setting the command in AutoVoice->Natural Language results in Error:null

 

Besides, the Tasker action AutoVoice Natural Language Context, despite not throwing an error, does not seem to work. The context isn't set.

 

Well, I'm trying to run a tasker profile that worked before the upgrade. So, I'm assuming that what I'm doing is correct.

My setup is the following. I have two intents one following the other. The first intent creates the output context X and the second intent accepts the input context X and the response it generates includes values of variables in the context. Some of those variables are set by the first intent, but some I would like to set in Tasker in response to the first intent. So, I tried the following:
1) Using a single context X and setting its variables using the Tasker AutoVoice action in response to the first intent. This makes it possible to activate the second intent which depends on context X (the context is set not only by the AutoVoice action but also the first intent). Still, the variables available to the second intent are only those set by the first intent, and not the AutoVoice tasker action.
2) Using two contexts X and Y, where X is created by the first intent, and Y is set by the tasker action. This will prevent the second intent from being activated at all (now it depends on two contexts). It seems that the tasker action does not set the second context.

 

Yes, I have both v1 and v2 tokens.