> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/performance/my-application-page-selfservice.md).

# Changing refresh time for my applications page in SelfService

Why a change to an application takes up to 50 minutes to appear on the My Applications page in SelfService, and which cache timer to shorten.

| Symptom                                                                        | Likely cause                                           | Resolution                                                            |
| ------------------------------------------------------------------------------ | ------------------------------------------------------ | --------------------------------------------------------------------- |
| An application was added or changed and does not appear on **My Applications** | The page is served from a cache swept every 50 minutes | [Shorten the sweep](#the-three-caches-behind-the-page)                |
| An application never appears, however long you wait                            | It has no URL set, or the user is not entitled to it   | [What makes an application appear](#what-makes-an-application-appear) |

## What makes an application appear

Three kinds of application can show on the page — authentication provider, content provider and URI pattern. The **authentication provider** is much the most common. A user sees only public applications and those they are entitled to.

**Each kind is included only if it has a URL.** That is the single gate they share: the page is built by listing each kind in turn and skipping any entry whose URL is blank, so an application with everything else configured is simply absent rather than broken.

### Authentication providers

An authentication provider needs two things — **a linked resource**, and **a URL on it**. A provider with no resource at all is skipped before the URL is even looked at.

{% hint style="info" %}
**Application URL on the provider and URL on its resource are the same value, not two places to try.** The provider screen's **Application URL** field is bound directly to the linked resource's URL, and the applications page reads that resource URL. Setting it on either screen sets the one value; if it will not save on one, it will not save on the other, and the thing to investigate is the save rather than which screen you used.
{% endhint %}

The name and icon on the tile come from the resource too, when it carries them — a display-name property overrides the provider's own name, and an icon property supplies the image. Without them the tile falls back to the provider name.

### Content providers

A content provider is included when **Show on Applications Page** is ticked *and* it has a URL. To keep one off the page, untick **Show on Applications Page**.

Whether a user then sees it is separate: ticking **Is Authorization Deactivated?** marks the provider public, and a public application is shown to everyone without an entitlement. That checkbox is the provider's public flag — the label is about authorization, the effect is visibility.

## The three caches behind the page

The page is served from three UI caches, each swept on its own timer. The 50 minutes a change can take to appear is the first of them:

| Property                                   | Default                | What it sweeps              |
| ------------------------------------------ | ---------------------- | --------------------------- |
| `org.openiam.application.sweeeptime`       | `3000000` — 50 minutes | The application list itself |
| `org.openiam.content.provider.threadsweep` | `300000` — 5 minutes   | Content providers           |
| `org.openiam.auth.provider.sweep.time`     | `60000` — 1 minute     | Authentication providers    |

{% hint style="info" %}
**`sweeeptime` has three e's.** That is the spelling the product uses — it is read as `org.openiam.application.sweeeptime` in `ApplicationCache` — so a corrected spelling is simply ignored and the 50-minute default stays in force.
{% endhint %}

Set them as `-D` arguments on the UI service — on **RPM** that is `CATALINA_OPTS` in `/etc/systemd/system/openiam-ui.service`. Lowering only the first is usually enough, since the other two are already shorter than it:

{% code overflow="wrap" %}

```
-Dorg.openiam.application.sweeeptime=60000
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/troubleshooting/performance/my-application-page-selfservice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.