No option to override errors with recent AI Studio update

English Forum AI Studio
1

I saw that the UI recently updated so that there no longer the ability to override flagged errors in AI Studio rules.

I have a rule that utilizes AI Studio to assign subtasks based on specific guidance, and despite adjusting the guidance to comply with the error, it is still flagging this as an error. Previously I was able to override the error so that I could save the rule (and the rule works as intended), but now I have no way to override the error, which has ultimately prevented me from modifying the rule any further as I can no longer save the rule until the error is resolved.

This is the error:

Task assignment requires objective criteria

For task assignment, “Use AI” is designed to assign tasks to users based on objective instructions. Asana AI is not designed to assign tasks via AI-based assessments of a user’s skills or traits. To publish your workflow, please either (i) revise your user assignment instructions to focus on objective factors or (ii) remove the “Use AI” option from the assignee field. For example, your workflow instructions could include these objective criteria: Operational conditions (e.g., availability, on-call status, office location) Role-based assignments (e.g., team membership, job function) Scheduling rules (e.g., rotation systems, predetermined schedules) Workload metrics (e.g., current task count)

And here is the guidance provided. Note that I am using AI to define the number of subtasks to create and the title of those subtasks in addition to the assignment of the subtasks. The “Approver” and “Reviewer” fields mentioned are Custom People Fields.

Subtask Creation

• Generate one subtask for each entry stored in the Approver and Reviewer(s) fields.

• If a field contains no entries, no subtask is generated from that field.

• If the same entry appears in both fields, generate only one subtask associated with the Approver field.

Subtask Assignment

• Populate the assignee field of each subtask using the corresponding entry from the field that produced it.

• Entries from the Reviewer(s) field populate the assignee field for Reviewer subtasks.

• Entries from the Approver field populate the assignee field for Approver subtasks.

• No additional evaluation, comparison, or interpretation is required.

Subtask Titles

• Subtasks created from Reviewer(s) use the title “Reviewer.”

• Subtasks created from Approver use the title “Approver.”

Is there something wrong with my guidance that I can adjust to resolve this error, or another way to override the error I’m experiencing?

1 Like
2

Hi @MattClark_iDO , thank you for flagging this.
I was trying to replicate your rule, but it did not produce the same error. In this instance, I would suggest working with our Support Team to try and find a resolution.

You can contact the Asana support team through our Asana Support chatbot, which can be found at the bottom-right of the Help Center homepage. This method allows us to collect more information about your issue and effectively place your ticket with the team best equipped to assist you.

Follow the steps below to get in touch with the Support Team:

Visit the Help Center homepage.

  • Click the chat icon in the bottom-right corner to open the Asana Support chatbot.

  • Briefly describe your issue in the chat window.

  • If the suggested Help Center articles do not resolve your issue, click Yes when asked, "Would you like support for this question?" to submit a ticket.

  • Enter your first and last name, email address, and any additional details about the issue.

  • The chatbot will attempt to identify the nature of your request; you can approve the selected topic or decline it and choose the topic from a list. General topics appear first, then more specific ones (e.g., Logging in > Password verification link).

  • Provide any other relevant details and attach files like screenshots if they would be helpful.

  • The chatbot will confirm that your request has been received. You’ll also receive an email at the address you provided. When logged in, you can view your newly opened case in the Asana Customer Portal.

3

Also having this issue Matt! Out of interest, is your rule part of a bundle? I am wondering if that’s related, as I have another rule that doesn’t seem to be throwing the error but it’s only sitting in a single project.

4

@Andrea_Carlaw - Yes! The Rule is part of a Bundle. Speaking with Asana’s support, it appears that there are TWO issues at play here. The first is the recent removal of the the Override button when errors appear in AI Studio rules. This is apparently being added back imminently.

The second issue relates to inconsistent handling of AI Studio errors when the rule is inside a bundle versus outside of a bundle, where the error wasn’t showing if the rule was built outside of a bundle, and only appeared when the rule was built inside of a bundle. I understand Asana’s engineering team is treating this is a separate issue.

5

I’m currently trying to implement a rule in a bundle doing something very similar to you Matt and having the exact same issue.

I guess I’ll just need to wait until tomorrow (or later) to see if there’s a fix.

6

Looks like the Override button is back.

1 Like