> ## Documentation Index
> Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deleting Old Signals

export const LwTemplate = ({title = "Key questions to get you started", icon = "sparkles", cta = "Powered by Agent Studio", linkHref = "https://lucidworks.com/demo/?utm_source=docs&utm_medium=referral&utm_campaign=docs_cta_ai"}) => {
  const [isLoaded, setIsLoaded] = useState(false);
  useEffect(() => {
    const timer = setTimeout(() => {
      setIsLoaded(true);
    }, 500);
    return () => clearTimeout(timer);
  }, []);
  return <div className="lw-template-container">
      <Card title={title} icon={icon}>
        {isLoaded && <span dangerouslySetInnerHTML={{
    __html: `<lw-template id="a029c1a9-28be-427e-b0e1-5d918920246a"></lw-template
            >`
  }} />}
        <Link href={linkHref} className="agent-studio-link text-left text-gray-600 gap-2 dark:text-gray-400 text-sm font-medium flex flex-row items-center hover:text-primary dark:hover:text-primary-light group-hover:text-primary group-hover:dark:text-primary-light">Powered by Lucidworks Agent Studio</Link>
      </Card>
    </div>;
};

[localhost link]: http://localhost:3000/docs/5/fusion/getting-data-out/query-enhancement/signals/deleting-old-signals

[mintlify link]: https://doc.lucidworks.com/docs/5/fusion/getting-data-out/query-enhancement/signals/deleting-old-signals

[old doc.lw link]: https://doc.lucidworks.com/fusion/5.9/468

Signals are not automatically deleted by default, and over time they occupy an increasing amount of storage space.

To avoid running out of storage space as a result of your growing collection of signals, you must decide on a signals retention policy, then configure and schedule a [REST Call job](/docs/5/fusion/reference/config-ref/jobs/rest-call) that regularly deletes old signals.

The duration for which signals should be kept depends on your use case and your organization’s policies. For example, in some cases signals could be deleted after 30 days, while in other cases they may remain useful for a year, or even forever.

<LwTemplate />

## Learn more

<Accordion title="Configure a REST Call Job to Delete Old Signals">
  1. Navigate to **Collections** > **Jobs**.
  2. Click **Add** and select **REST Call**.\
     The REST Call job configuration panel appears.
  3. Enter an arbitrary ID for this job, such as "Delete-old-signals".
  4. Enter the following endpoint URI, substituting the name of your signals collection for `signalsCollectionName`:
     ```bash theme={"dark"}
     solr://signalsCollectionName/update
     ```
  5. In the **Call Method** field, select "post".
  6. Under **Query Parameters**, enter the property name "wt" with the property value "json".
  7. In the **Request entity (as string)** field, enter the following:

     ```html wrap theme={"dark"}
     <root><delete><query>timestamp_tdt:[* TO NOW-2WEEKS]</query></delete><commit /></root>
     ```

     See [Working with Dates](https://solr.apache.org/guide/8_6/working-with-dates.html) for details about date formatting.

     Your job configuration should look similar to this:

       <img src="https://mintcdn.com/lucidworks/vupE2UCZdg04NdXx/assets/images/4.2/signals-delete-job.png?fit=max&auto=format&n=vupE2UCZdg04NdXx&q=85&s=b9fead537a4ecf27ca286d4ac6b10e86" alt="Signals delete job configuration" width="1758" height="1329" data-path="assets/images/4.2/signals-delete-job.png" />

  <Tip>You can configure a schedule for this job at **System** > **Scheduler**.</Tip>
</Accordion>
