I struggled with AI-Studio’s rules for the first time in a while.
It had been working properly for the past two months, so I hadn’t made any changes. When I tried to make some changes, it didn’t work properly.
The following Guidance for AI works as expected.
"Action:
Create a new task and enter the following in the task description.
Select a task from the project’s task section.
- Enter tasks from the “Schedule” section in the [Schedule List] part of the description.
- Enter tasks from the “Announcements” section in the [Announcement List] part of the description."
When I tried the same process as below, I tried adjusting and testing it many times, but it never worked.
It responded that it recognized the first field, but couldn’t find the second.
"Action:
Create a new task and enter the following in the task description.
Select tasks within the project from the field values (single-select).
- Enter tasks whose “Processing Type” field is “Schedule” in the [Scheduled List] part of the description.
- Enter tasks whose “Processing Type” field is “Announcement” in the [Announcement List] part of the description."
In summary, specifying a section allows me to extract tasks, but specifying a field doesn’t work properly.
Do you have any advice?
I’ve run into this a few times. When sections work but custom-field filters don’t, it’s usually a field “identity” or scope issue rather than the rule logic.
Try these quick checks:
-
Confirm it’s the same field instance everywhere
Open Customize in your project and make sure “Processing Type” is added there. If you ever created a similarly named field elsewhere, some tasks might be using a different “Processing Type.” The rule can recognize one value, then fail to find the second if it belongs to a different field instance.
-
Verify the exact option text on your target tasks
Open a few tasks you expect to match. Make sure the single-select values are exactly “Schedule” and “Announcement” with no extra spacing, punctuation, or emoji variants. Tiny differences can break matching.
-
Check project scope with multi-homed tasks
If tasks are in multiple projects, ensure the project running the rule has the Processing Type field added and that the values live in that project context.
-
Isolate the failing value
Run two separate tests: one that pulls only “Schedule,” then one that pulls only “Announcement.” If one works and the other doesn’t, it’s almost always a duplicate field or a slightly different option label on the second.
-
Normalize the field if needed
If you suspect duplicates, remove “Processing Type” from Customize, add the correct shared field back, and update the affected tasks so they all reference the same field instance.
If it still misbehaves, could you share a minimal repro with Support so we can look at logs? Steps here: https://help.asana.com/s/article/how-do-i-get-support-from-asana?language=en_US
1 Like
Hi @Stefan_Kirilov
Thank you for your advice.
From my testing, the situation was as follows.
Preparation
- Create a single-selection field in the project.
- Register ABC and DEF as the values of the single-selection field.
- Create six tasks in the project.
- Set the field value for three tasks to ABC.
- Set the field value for three tasks to DEF.
Instruct the following tasks in AI-Studio using rules.
- Task 1: Extract tasks with the field value ABC and list them in the description field of the specified task.
- Task 2: Extract tasks with the field value DEF and list them in the description field of the specified task.
Execution results
- Instruction: Perform Task 1 first, then Task 2.
Task 1 can be performed, but Task 2 responds that there is no corresponding task.
- Instruction: Perform Task 2 first, then Task 1.
Task 2 can be performed, but Task 1 responds that there is no corresponding task.