Notifications
Announcements
I enabled the upcoming feature "Enable a modern Timeline control experience" in the app settings. After enabling it, I can no longer load the timeline in some of my records (error loading control).
The following error is displayed: "React error #31 – Objects are not valid as a React child (found: [missing argument]). If you meant to render a collection of children, use an array instead."
I've been able to narrow down the issue to specific customer emails. If I remove the reference between the email and the record(case), the timeline control starts working again. However, I can't identify the exact reason why a single email would cause the control to crash. At first glance, these seem to be emails with a lot of graphical content, such as logos and formatting. As soon as I disable the feature again, everything works as expected, and even the emails that previously caused the issue are displayed correctly.
Is anyone else experiencing the same issue or has made more progress in finding the root cause?
this issue with the modern Timeline control in Power Pages causing a React error #31 when loading certain records has been reported by other users in the Power Platform Community forum .
Error Message: "React error #31 – Objects are not valid as a React child (found: [missing argument]). If you meant to render a collection of children, use an array instead."
"React error #31 – Objects are not valid as a React child (found: [missing argument]). If you meant to render a collection of children, use an array instead."
Trigger: The error occurs when loading timeline data for records linked to specific emails, especially those with rich graphical content (logos, formatting, embedded HTML).
Workaround: Removing the email reference from the record (e.g., case) allows the timeline to load correctly. Disabling the modern timeline feature also resolves the issue.
The error suggests that the React rendering engine is encountering a malformed or unexpected object—likely from the email content—that it cannot render as a child component. This could be due to:
Disable the Modern Timeline Feature Until Microsoft releases a fix, it's safest to keep the feature disabled if your records include rich email content.
Log a Support Ticket with Microsoft This issue is under review but not yet resolved. Logging a ticket will help escalate it and provide Microsoft with more examples.
Sanitize Email Content If feasible, preprocess or sanitize email content before linking it to timeline-enabled records. Strip out problematic HTML or convert it to plain text.
Use Classic Timeline Temporarily The classic timeline control handles these emails without crashing, so it’s a viable fallback.
🏷️ 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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 793 Most Valuable Professional
Michael E. Gernaey 333 Super User 2025 Season 2
Power Platform 1919 268
