web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Could not train your m...
Power Automate
Suggested Answer

Could not train your model. Try again later

(2) ShareShare
ReportReport
Posted on by 4
Hello,
 
I'm creating a new AI model for invoices in AI builder but can't train it once I have all documents tagged. Once I click Train button I got the following message:
 
 
Any idea of what could be happening?
 
Thanks in advance
Categories:
I have the same question (0)
  • Suggested answer
    Jon Unzueta Profile Picture
    1,827 Super User 2025 Season 2 on at
     

    Thanks for the details! Based on your issue with training an AI Builder invoice model after tagging all documents, here’s a summary of what might be going wrong and how to resolve it:


    ⚠️ Common Reasons Why Training Fails After Tagging

    1. Incorrect or inconsistent tagging:

      • If a field is tagged in some documents but marked as "Not in document" in others, it can confuse the model.
      • Double-tagging or overlapping tags can also cause training to fail  .
    2. Collections not properly processed:

      • If you're using multiple collections (e.g., per vendor), the model might average detection across all collections, which can lead to missing fields during training  .
    3. Missing or unreadable documents:

      • PDFs must be readable and not image-only unless OCR is enabled.
      • Ensure all documents are fully loaded and tagged before training.
    4. Model limitations:

      • AI Builder has limits on document size, number of fields, and training time. If exceeded, training may silently fail  .

    🛠️ Troubleshooting Steps

    Here’s what you can try:

    ✅ Step 1: Review Tagging Consistency

    • Go through each collection and ensure all required fields are tagged consistently.
    • Avoid marking fields as “Not in document” unless absolutely necessary.

    ✅ Step 2: Retag Problematic Documents

    • If you suspect a specific document is causing the issue, retag it manually.
    • A known workaround is to re-tag all fields in the document that triggers the error  .

    ✅ Step 3: Reduce Complexity

    • Try training with fewer collections or fewer documents to isolate the issue.
    • Start with one collection and gradually add more.

    ✅ Step 4: Use Microsoft’s Guidelines

    Refer to the official documentation:


    🧠 Pro Tip

    If you’re working with many vendors and invoice formats, consider using Microsoft Syntex or custom AI models in Azure Form Recognizer, which offer more flexibility and control.

     

    🏷️ Tag me if you have any further questions or if the issue persists.

    ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.

    ❤️ Give it a Like if you found the approach useful in any way.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 519 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 296 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard