----------- Original Email -----------
You are receiving this notice because you are running the Task Queues service with a custom domain on the following application(s):
s~ddtor3
Currently, we have a bug in the system where tasks enqueued from a custom domain (e.g. your_domain.com) are always routed to the default module even if a non-default module is specified in the app's dispatch.yaml/xml file. This bug will be fixed by February 22, 2016.
No action is required on your part if your application expects documented behavior (Java documented behavior).
However, if your application depends on the existing behavior of tasks being routed to the default module, then you must add an entry to your dispatch.yaml/xml before February 22, 2016 that routes your Task Queues endpoint to the default module. You can read more about dispatch.yaml/xml here. Example entry:
- url: "*/my/task/queue/url/*"
module: default
This is the expected behavior after the fix:
Have an application with a domain (e.g. your_domain.com) mapped to it
Configure two modules, and a dispatch rule to route all */api/* traffic to the non-default module.
Add a task to the queue from the custom domain and the default module, with a URL of /api/taskqueue (e.g. your_domain.com/api/taskqueue)
The task should be run on the non-default module, where */api/* is routed.
