The forecast interval is a one-time choice

About five minutes of reading

Scheduling and capacity planning both wait on a forecast, and the interval cannot be edited later.

Forecasting predicts contact volume and handle time from historical metrics. Short-term forecasts update daily and are the input for scheduling up to 18 weeks ahead. Long-term forecasts update every week, on the weekday you created them, and are the input for capacity planning up to 64 weeks ahead.

Before any of that, set the forecast and schedule interval to 15 or 30 minutes. The interval page says you need Forecast and schedule interval - Edit, you must set it before you create forecast groups, and you cannot change it later. Intraday forecasts update every 15 minutes, and only for a queue-channel with at least 5,000 unique contacts a week over the last 4 weeks.

• The first short-term or long-term forecast is typically ready within 4 hours, and often in about 1 hour.
• Only the newest forecast stays on the page. Download a copy if you need to keep that day.
• The forecasting page lists the order: interval, forecast groups, historical import, create, inspect, publish.
• A change to the forecast group, such as adding or removing a queue, starts that computation again.

Number on this page: Interval 15 or 30. Minutes. Set once. Cannot be changed.

Picture from this room.

1. Permission. Forecast and schedule interval - Edit.
2. Choose. 15 or 30 minutes.
3. Group. Queues that share a forecast.
4. Publish. Hand it to schedulers.

What usually goes wrong: Trying to change 15 minutes to 30 minutes after the first forecast group exists.

Set the forecast and schedule interval in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Glossary

• Start media streaming Sends live customer audio to Kinesis Video Streams for a third-party recorder or bot.
• Screen recording Records the agent desktop. On the Basic price list it is 0.006 USD per minute.
• Forecasting and agent scheduling The 4 Aug 2026 name for native WFM: forecast, capacity, schedules, and adherence.
• Schedule adherence How closely an agent's actual status matched the published schedule. Native metrics appear after schedules are published. Third-party WFM reads agent events.

Mind map

Open the Ecosystem mind map

Sister technologies

Connect answers the contact. Workforce, quality, emergency location, and the system of record sit beside it, and they only stay honest if they share ContactId.

Config and troubleshooting

Trying to change 15 minutes to 30 minutes after the first forecast group exists.

Adherence needs agent events, not a person refreshing a report. ResourceType AGENT_EVENTS and StorageType KINESIS_STREAM is the hook. A second consumer should read the stream, not a second delivery on the instance.

InstanceStorageConfig

Resources:
  AgentEvents:
    Type: AWS::Connect::InstanceStorageConfig
    Properties:
      InstanceArn: !GetAtt CampusInstance.Arn
      ResourceType: AGENT_EVENTS
      StorageType: KINESIS_STREAM
      KinesisStreamConfig:
        StreamArn: !GetAtt AgentStream.Arn

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.