Schedules: Track Recommendation Task Runs

Overview

The Schedules page shows recommendation implementations that were scheduled from Spotto instead of run immediately. It gives you one place to review what is queued, which subscriptions or resources are in scope, when the run is expected, and what happened the last time Spotto touched it.

What you can do

• Review scheduled recommendation implementations across the selected subscriptions.
• Search by recommendation, schedule ID, resource name, subscription, or action target.
• Filter by schedule type, target type, and scope.
• Open a schedule to inspect its status, next run time, last run details, notes, and target context.

Where to find it

In the Spotto Portal, go to Tasks -> Review -> Schedules.

How schedules get here

Schedules appear here when a user opens a supported recommendation, chooses Implement, and then configures a scheduled run instead of running the action immediately.

Today, recommendation scheduling is a one-time scheduled implementation flow.

What the page shows

The schedules list is designed as a task view rather than a recommendation inbox. Each row shows the main details you need before opening the schedule:

• Name: the schedule name or the derived recommendation/action label.
• Scope: the affected subscription, selected resources, or provider scope.
• Target: the recommendation action and the resource or resource set it applies to.
• Status: whether the schedule is active, paused, or has a failed last dispatch.
• Next Run: the next expected execution time and timezone.
• Last Run: the last execution time and the last known run ID.

What you can inspect in schedule details

Select a row to open the schedule detail view. This is where you can confirm:

• The schedule ID for support or audit follow-up.
• The recommendation and action being scheduled.
• The current schedule status.
• The next run time and last run time.
• Resource or subscription scope.
• Notes or configuration captured when the schedule was created.

If the target recommendation still exists in Spotto, the detail page can also take you back to the recommendation context.

Report schedules

The Report Scheduler company feature set is off and hidden by default. Enable it explicitly using the company's Feature Sets controls before using report schedules. With the required reporting and schedule permissions, open Generate → Report Schedules, then choose New Report Schedule. The Reports tab in Task Schedules shows the same schedules. Choose Background Reports to inspect generation and delivery history or generate an on-demand report. Users also need reporting/export permissions to generate a Service Delivery Report or Current State Analysis. Resource schedules retain their existing access behavior.

Choose a name, company timezone, fixed Azure subscription scope, report settings and an optional Action Group. Select a one-time run or a daily, weekly, monthly or quarterly recurrence. Recurring Service Delivery Reports can use the previous calendar month or quarter. Current State Analysis describes the collected state used by that run.

Calendar rules use the selected timezone. A nonexistent day, such as February 31, is skipped; choose the last day of the month when that is your intention. Quarterly runs use January, April, July and October. A daylight-saving gap is skipped, and a repeated local time runs once at its earliest occurrence. A one-time run cannot use a nonexistent local time.

Use Pause to stop future occurrences and Resume to continue. Editing, pausing or deleting a schedule does not cancel jobs already accepted. Open the schedule's jobs to follow each generation and delivery outcome and download an available report. Delivery failures retain the document. See background reports for recipient confirmation and review status.

A company can have up to 20 active report schedules. Pause or delete an existing schedule before activating another when you reach the limit. If an interrupted save leaves the limit unavailable after you have checked the active schedules, contact support before repeating the request.

Historical catch-up is limited to one year. Older missed periods are recorded as failures and scheduling moves to the next future occurrence. Contact support if you need to investigate a long interruption.

How recommendation scheduling works

At a high level:

1. Open a recommendation that supports Implement.
2. Start the implementation flow.
3. Choose the schedule option instead of running the action now.
4. Set the schedule time, timezone, name, and optional notes.
5. Save the schedule.
6. Review the created task under Tasks -> Review -> Schedules.

How this differs from recommendation management

Recommendation Management is for triage: prioritise, dismiss, restore, comment, and share. The Schedules page is for tracking work that has already been turned into a scheduled implementation task.

Use them together:

• Use Recommendation Management to decide what should happen.
• Use Remediation Actions to understand supported implementation flows.
• Use Schedules to review the tasks created from those scheduled implementations.

Troubleshooting

I scheduled a recommendation but do not see it on the Schedules page

What you're seeing: The schedule list is empty, or the schedule you just created is missing. Likely causes:

• The schedule was created in a different company context.
• The relevant subscription is not selected.
• The recommendation was run immediately instead of scheduled.
• The schedule creation failed before it was saved. How to fix:

1. Confirm you are in the correct company.
2. Select the subscription where the recommendation lives.
3. Search by recommendation name, resource name, or schedule ID if you have it.
4. Reopen the recommendation and check whether the implementation shows as scheduled or already executed.

I do not see a schedule option when implementing a recommendation

What you're seeing: The recommendation has Implement, but you do not get a schedule workflow. Likely causes:

• The implementation flow did not reach the schedule step.
• The schedule was not saved. How to fix:

1. Reopen the recommendation and start Implement again.
2. Complete the schedule fields and save the task.
3. If the schedule step still does not appear, capture the recommendation ID and contact support.

The schedule exists, but the run did not happen yet

What you're seeing: A schedule is present, but the recommendation has not been implemented yet. Likely causes:

• The scheduled time has not been reached.
• The timezone on the schedule is different from the timezone you expected.
• The last dispatch failed. How to fix:

1. Open the schedule detail page and confirm Next Run and timezone.
2. Check the current status and last run status.
3. If the time has passed and the schedule still did not run, capture the schedule ID and contact support.