Introduction
Use this article when DatuAI does not return the expected result, an update fails or stops part-way through, or you need help understanding a DatuAI message or behavior.
Data Access and Scope
What Should I Check if DatuAI Returns No Results?
DatuAI answers from information that exists in the design where the chat was opened. If a request returns no result, confirm that the field or relationship required for the question has been defined and populated.
For example:
- A question about late starts requires both Planned Start and Actual Start.
- A question about material requires the applicable material property to exist and contain values.
- A question about activity relationships requires the design objects to be linked to activities.
A correctly written request cannot return information that does not exist in the design.
Can DatuAI Work Across Multiple Designs?
No. Each DatuAI chat works with one design at a time. To work with another design, open DatuAI from that design instead.
Why Are Some 2D CAD Elements Unavailable to DatuAI?
DatuAI works with DatuBIM design objects rather than raw CAD geometry. IFC elements are already object-based. For 2D CAD files, the applicable geometry must first be converted into DatuBIM objects using Identify Objects or Manage Objects.
Activity progress percentages, amounts, quantities, and similar activity-management information are outside the current DatuAI chat scope. Use the applicable Tracked Activities, Gantt, or Progress Dashboard workflows for that information instead.
Can I Update Multiple Objects at Once?
Yes. Any number of objects can receive the same value in one request. For example: "Set the Actual End of all objects of type H to July 23 2026."
If different groups of objects require different values, group the objects by value and send separate requests.
Can I Update Multiple Fields on the Same Object?
Yes. Several supported fields on the same object can be updated in one request. This can be especially useful for related date fields because DatuBIM validates the applicable values together.
Why Is DatuAI Asking Me to Clarify a Field Name?
A field name may exist in more than one place. For example, a field such as Actual End may exist as an activity-related field and as a custom property. When a request is ambiguous, DatuAI asks which field you intend to use before making the change.
Answer the clarification directly. The clarification applies to the full request.
Why Was My Update Rejected?
DatuAI applies the same validation rules used elsewhere in DatuBIM. If DatuBIM would reject a value, DatuAI will also reject it and report the reason.
For example, a date update may be rejected if it would result in an Actual Start later than the Actual End. Review the reported reason, correct the applicable value or related field, and try again.
Which Values Can DatuAI Clear?
DatuAI can clear supported custom properties, Actual dates, and Inspection information. Planned Start and Planned End cannot be cleared. They can be changed to another valid date but cannot be left empty.
Large and Interrupted Requests
Why Is DatuAI Asking Me to Confirm a Large Update?
For very large changes, DatuAI prepares the update before writing anything. If you see a message similar to:
This will update N objects...Reply yes to start.
Nothing has been changed yet. Reply yes to begin the update. If no confirmation is provided, the request expires after approximately 15 minutes.
How Do I Check the Status of a Large Update?
While a large update is running, reply status. DatuAI will report the current progress of the background operation.
Can I Cancel a Large Update?
Yes. Reply cancel to stop an update that is already running. Objects updated before the cancellation remain changed and are included in DatuAI's response.
What Should I Do if an Update Stops Part-Way Through?
Review DatuAI's response before sending another request. If some objects were already updated, the response identifies them. Do not resend those objects. Send only the remaining objects that still need to be updated.
What Should I Do if a Request Contains Too Many Changes?
A request can become too complex when it combines many different objects, fields, and values. Split the work into smaller requests. The most reliable pattern for updating multiple objects is one field + one value per message. If some objects were updated before the request stopped, do not include them again.
What Should I Do if the Same Request Repeatedly Fails?
Do not continue resending the same failed large request in the same conversation. Open a new DatuAI chat and continue with the remaining work there. A new chat begins with a clean context.
Chat Availability and Data Refresh
Why Is the Chat Unavailable While Design Data Is Updating?
After a large update, the design data may need time to refresh. If DatuAI reports that the chat is unavailable while design data is updating, wait for the design update to finish and try again. The chat should become available once the refresh is complete.
Why Is Recently Changed Data Not Reflected in DatuAI?
Changes made elsewhere in DatuBIM may not immediately appear in a chat that is already open. Wait for the design to finish updating and ask again. If needed, open a new chat to work from the latest design state.
Can I Upload Files or Images to DatuAI?
DatuAI currently accepts text input only. Excel files, screenshots, images, charts, and other files cannot currently be provided directly to the chat.
Is There a Message-Length Limit?
The input box currently supports up to 5,000 characters. Longer pasted content may be cut off, so divide larger text or data into smaller requests.
Use an unambiguous date format such as July 23 2026 or 07-23-2026. Avoid slash dates such as 7/23/2026, because they may be interpreted differently depending on regional settings.
DatuAI Message Quick Reference
If You See Or Experience... | What it Means / What to Do |
"This will update N objects...Reply yes to start." | A large update has been prepared, but nothing has changed yet. Reply yes to begin. Confirmation expires after approximately 15 minutes. |
DatuAI finds more than one matching field | The field name is ambiguous. Identify which field you mean; the clarification applies to the full request. |
A request stops after some objects were changed | Review the response and resend only the objects that were not already updated. |
A request contains too many different changes | Divide the work into smaller requests, preferably one field and one value per message. |
Chat is unavailable while design data is updating | The design is refreshing. Wait for the update to complete before trying again. |
A value is rejected | DatuAI is applying DatuBIM's normal validation rules. Review the reported reason and correct the applicable value. |
| A request returns no result | Confirm that the required property, date, or relationship exists and is populated. |
A large request repeatedly fails | Open a new chat and continue with the remaining objects. |
If the issue continues, first confirm:
- You are using DatuAI for the correct design.
- The design objects required for the request exist.
- The applicable properties have been defined and populated.
- Schedule-based questions have the required schedule relationships and dates.
- The request fits within the current DatuAI scope.
- A large or complex request has been divided into smaller requests where appropriate.
- Recently changed design data has finished refreshing.
- You have reviewed DatuAI's full response for failed, skipped, or already-updated objects.
When reporting an issue, provide:
- The site and design being used.
- The request entered into DatuAI.
- DatuAI's complete response.
- The affected object or property names, when applicable.
- A screenshot or recording of the unexpected behavior, when applicable.
Still Need Help?
If DatuAI continues to behave unexpectedly after the applicable troubleshooting steps, reach out to your Datumate Customer Success Manager.