<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with retention]]></title><description><![CDATA[A list of topics that have been tagged with retention]]></description><link>https://fusionauth.io/community/forum/tags/retention</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 21:07:11 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/retention.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[How to prevent performance issues from unbounded login history growth?]]></title><description><![CDATA[<p dir="auto">To prevent performance degradation from unbounded login history growth, you should configure a retention period in your Login Record Settings rather than keeping unlimited history.</p>
Recommended Configuration

Navigate to <strong>Settings → System → Advanced → Login Record Settings</strong>
Enable auto-deletion of login records
Set a retention period (365 days is a common best practice)
Once configured, records older than your specified retention period will be removed on a rolling basis

What to Expect

<strong>Zero downtime</strong>: This is a simple configuration change that does not require any system downtime
<strong>Initial cleanup</strong>: After setting the retention period, FusionAuth will automatically delete existing records that exceed the retention threshold. Any existing login records older than the configured number of days become eligible for deletion based on this configuration — they are not grandfathered in.
<strong>Rolling maintenance</strong>: Going forward, old records are automatically cleaned up, preventing the tables from growing indefinitely

Implementation Options
<p dir="auto">You can make this configuration change yourself during a convenient time. The change can be applied through:</p>

<strong>Admin UI</strong>: Navigate to Settings → System → Advanced → Login Record Settings
<strong>System Configuration API</strong>: Use a PATCH or PUT request to /api/system-configuration with the loginRecordConfiguration settings
<strong>Terraform</strong>: Configure the login_record_configuration block in your system configuration resource

<p dir="auto">This proactive maintenance helps ensure your FusionAuth instance remains performant as your user base and login volume grow over time.</p>
Related Documentation

<a href="https://fusionauth.io/docs/apis/system/update-the-system-configuration#request-body" rel="nofollow ugc">Update System Configuration API - Request Body</a> - Details on configuring login record retention via API, including the loginRecordConfiguration.delete.enabled and numberOfDaysToRetain parameters
<a href="https://registry.terraform.io/providers/FusionAuth/fusionauth/latest/docs/resources/system_configuration#argument-reference" rel="nofollow ugc">Terraform System Configuration Resource</a> - Configuration reference for managing login record settings with Terraform
<a href="https://fusionauth.io/docs/apis/login/search" rel="nofollow ugc">Search Login Records API</a> - API for searching and paginating through login records
<a href="https://fusionauth.io/docs/apis/login/export" rel="nofollow ugc">Export Login Records API</a> - API for exporting login records to CSV format

]]></description><link>https://fusionauth.io/community/forum/topic/3372/how-to-prevent-performance-issues-from-unbounded-login-history-growth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3372/how-to-prevent-performance-issues-from-unbounded-login-history-growth</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>