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

# Automation Budget Settings

> Set a monthly credit limit for automations, imports and scheduled jobs, get a notice before it runs out, and see what automations spent this month.

![WISEPIM automation budget showing credits used by automations this month and the choice between no limit and a monthly limit](https://mintcdn.com/swiftsyncai/mhFSeqbOqnn6iTdk/images/marketing-screenshots/settings/settings-ai-budgets-light-branded.webp?fit=max\&auto=format\&n=mhFSeqbOqnn6iTdk\&q=85\&s=8c97576762f97d10f6ef85eadabaccd0)

The Automation budget puts a ceiling on the credits that unattended work can use each month: workflow AI steps, enrichment after an import, scheduled enrichment and scheduled Catalog Jobs. Runs you start yourself are not affected. They always use your normal credit balance.

**What this page enables:** you can let automations run freely without worrying that a busy month, a large import or a misconfigured workflow drains your credits.

**Where to find it:** go to **Settings** and open **Automation budget** in the AI & Content group. The [AI review](https://docs.wisepim.com/en/settings/ai-review.md) page links here from its header too.

> [!NOTE]
>
> This is a cap, not an allocation. It does not set credits aside. Two other controls limit spending in different ways: monthly caps per team member in [Usage Settings](https://docs.wisepim.com/en/settings/usage.md), and credit budgets per project in [Organization Settings](https://docs.wisepim.com/en/settings/organization.md).

## This month

The **This month** section shows what automations spent since the first of the month:

* Without a limit: "120 credits used by automations" with "No limit is set, so automations can use any credits you have."
* With a limit: "120 of 500 credits used" with a **Credits used this month** meter and a marker for your notice threshold, such as "Notice at 80%".

## Set a monthly limit

Under **Monthly limit**, choose **Limit for automations**:

| Option | What happens |
| - | - |
| **No limit** (default) | Automations can use any credits you have. |
| **Set a monthly limit** | When automations reach the limit, they pause until next month and you get a notice. |

With a limit, fill in two fields:

| Field | What it does | Range |
| - | - | - |
| **Credits per month** | The cap for unattended work. 0 pauses AI work from automations. | 0 or more |
| **Send me a notice at (%)** | One notice per month when automations reach this share of the limit. | 10 to 100, default 80 |

WISEPIM shows a suggested amount, such as "Suggested: 1,000 credits, half of your plan's monthly credits." Click **Use 1,000** (or whatever amount is shown) to fill it in. The suggestion never applies itself.

Save your changes. You see "Automation budget saved". Only project owners and admins can change the budget.

## What counts as automation

| Counts toward the budget | Does not count |
| - | - |
| AI steps in workflows | Enrichment, translation or other runs you start yourself |
| Enrichment that runs after an import | Catalog Jobs you start by hand |
| Scheduled enrichment | |
| Scheduled Catalog Jobs | |

## When the limit is reached

WISEPIM checks the budget before it starts unattended work. If the estimated cost doesn't fit in what is left this month, the work is skipped and does not start. Work that is already running always finishes, so spending can end up slightly over the limit.

You get two in-app notices at most per month:

| Notice | When |
| - | - |
| "Your automation budget is nearly used" | Spending reaches your notice percentage. |
| "Automations paused: monthly budget reached" | The limit is reached. The message tells you to raise the limit to keep automations running. |

The budget resets on the first day of each calendar month. Refunds for failed work in the same month free up budget again.

## Act on what you find

> **Automations paused in the middle of the month**
>
> Raise **Credits per month**, or switch to **No limit**, so the next automated runs can start. Runs you start yourself keep working in the meantime.

> **You don't know what limit to set**
>
> Start with the suggested amount and keep the notice at 80%. Check what automations spent at the end of the month in [Usage Settings](https://docs.wisepim.com/en/settings/usage.md) and adjust.

> **You want to stop all automation spending for now**
>
> Choose **Set a monthly limit** and enter 0 under **Credits per month**. Runs you start yourself keep working.

> **A teammate burns credits with manual runs**
>
> The automation budget doesn't cover manual runs. Set a monthly cap per member in [Usage Settings](https://docs.wisepim.com/en/settings/usage.md) instead.

## Related

> **[Usage Settings](https://docs.wisepim.com/en/settings/usage.md)**
>
> See where credits go and cap spending per team member.

> **[Organization Settings](https://docs.wisepim.com/en/settings/organization.md)**
>
> Share one credit pool across projects and give each project a budget.

> **[AI Review Settings](https://docs.wisepim.com/en/settings/ai-review.md)**
>
> Decide which AI changes are saved right away and which wait for you.

> **[Catalog Jobs](https://docs.wisepim.com/en/products/catalog-jobs.md)**
>
> Schedule catalog-wide jobs whose spending counts toward this budget.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.