Recommendations and schedule

Two tabs of the Limits screen hold things that are waiting: Recommendations holds changes waiting for a decision, and Schedule holds changes waiting for a date. The number next to the Recommendations tab counts the individual recommendations and batches open in it.

Recommendations

The summary at the top

Three cards summarize the batches listed in the tab; individual recommendations are not included. They show Total Exposure before and after, Average per line before and after, and the Variation, as an amount and as a percentage, green when exposure grows and red when it shrinks. Below them, a bar splits those changes into Increase, Decrease, Enable and Disable.

The table

The table mixes three kinds of row, told apart by the Type column:

Individual: a recommendation for one customer, usually produced by a policy or a workflow that evaluated that customer.
Batch: a group of changes created together, from a file, a segment adjustment or a policy run. Its row shows the totals of the whole batch.
Failed: the lines of an applied batch that could not be applied, grouped in one row per batch.

For each row you see the customer or batch, the type of change, the Observed Limit (the current one), the Recommended Limit, the Variation, the status and the request date. A customer who has no limit yet shows New instead of a percentage, because there is nothing to compare against.

The search bar filters by customer and by date range, and the footer counts how many individual recommendations, batches and failed lines are listed.

Acting on individual recommendations

Click an individual row to open its review card, or View all to go through every pending one in order. The card shows the current and new limit, the variation, and any attachment the policy produced, such as a recommendation report.

Accept approves the recommendation, and it is applied right away. If the approval is recorded but the application cannot start, the screen says so and gives the reason, and you can apply it from its batch.
Discard rejects it. Nothing changes on the line.
Edit the suggested limit lets you change the amount before accepting. The card keeps the original value visible, AltScore suggested followed by the amount, and Restore puts it back.

Only pending individual recommendations are listed. A line that failed when it was applied appears inside the Failed row of its batch instead.

Acting on batches

Click a batch row to expand it and see its lines. The expanded list shows up to a fixed number of lines per batch; when there are more, the row says so, and the totals on the row always cover the whole batch.

The button on the row opens the batch detail page. It reads Review and apply while the batch is waiting for someone, and View detail when there is nothing left to approve, because it is already applying or applies on its own. Applying, discarding and adjusting individual lines all happen on that page. See Tracking a batch.

When some customers in a batch have no current limit recorded, the observed total is shown with a ≥ sign and in a lighter color. Those customers count as zero, so the real total is at least that amount; hovering over the number says how many customers are missing a limit.

Failed lines

A Failed row, Failed in followed by the batch label, collects the lines of a batch that were not applied. Expand it to see each line with its error, or use View error on a line to read the reason. View detail takes you to the batch, and Retry, shown when the batch ended Completed with errors, applies the failed lines again. A retry covers every failed line of that batch, not only the one you are looking at, and the confirmation tells you how many lines that is.

Schedule

Schedule answers one question: what is going to activate or revert, and when. It lists recent batches that were given an activation or an expiry date; a batch with no dates never appears here.

The first thing on the tab is the state of the hourly check that acts on these dates. When it reads The hourly check is active., with the time of the next run, the dates below will be honored. When it says the check is paused or could not be reached, in red, nothing on the list will activate or revert until it is fixed. That is the moment to tell your administrator, not to wait and see. The refresh button next to the banner reads the tab again.

The list

The list is chronological. A batch with both dates appears twice, once for the activation and once for the expiry, because those happen on different days and either one can be the one you are waiting for.

Each row shows:

the batch label, which opens its detail page;
Activates or Reverts;
the date and time, and restores the segment too when the expiry also puts customers back in their previous segment;
Overdue in red when the date passed and nothing happened yet, or Done once the date is behind it (an activation also shows Done when the batch was discarded or could not be applied on its own);
for a completed revert, the counts of Reverted, left untouched and failed lines.

How to act on it

The Schedule tab shows dates but has no actions of its own. To apply, discard or retry a batch, open it from its label.

An Overdue row that is less than an hour old needs nothing: the check has not run yet. One that stays overdue well past the hour points to a problem with the check or with the batch. Open the batch to see its status, and tell your administrator if the banner is not green.
A revert with lines left untouched needs a decision. Those lines were changed by someone during the temporary window, so they still carry a limit that was meant to be temporary. Decide whether to keep it or to load a new change for them.
A batch with an expiry but no activation date waits for someone to apply it, and this tab does not say so. If it is not applied before the expiry, it can no longer be applied. See Temporary changes.

Batches are not filtered by test mode, so this tab shows the same rows with test mode on or off.

Recommendations and schedule