Common Issues

Common Issues

This page covers the most frequently encountered issues and their solutions.

Scheduling Issues

Resources Not Being Scheduled

Symptoms:

• Tagged resources aren’t starting/stopping
• No activity in Dashboard
• Schedule exists but nothing happens

Possible Causes & Solutions:

Verification Steps:

1. Navigate to Project Defaults
2. Confirm the service type is enabled
3. Confirm the region is listed
4. Navigate to Accounts > Manage
5. Verify account shows “Configured”
6. Check that resource tag matches schedule name exactly

Schedule Running at Wrong Time

Symptoms:

• Resources start/stop at unexpected times
• Time offset from expected schedule

Solutions:

1. Check timezone - Verify schedule timezone matches your intent
2. UTC conversion - SkySaver stores times in the selected timezone
3. DST handling - Be aware of daylight saving time transitions

Resources Staying Running

Symptoms:

• Resources don’t stop when period ends
• Continuously running despite schedule

Solutions:

1. Verify the stop time in your period
2. Check if another period overlaps
3. Confirm no AWS events are restarting resources
4. Review CloudTrail for manual interventions

Account Issues

Account Shows “Unconfigured”

Symptoms:

• Account status shows unconfigured
• “Check” button doesn’t change status

Solutions:

1. Verify CloudFormation template was deployed successfully
2. Check that role name matches (default: SkySaverScheduler)
3. Verify External ID matches Project Defaults
4. Ensure the template was deployed in the correct AWS account

Can’t Add Account

Symptoms:

• Error when adding account ID
• Account doesn’t appear after submission

Solutions:

1. Verify account ID is 12 digits
2. Check for leading zeros
3. Ensure account isn’t already added
4. Verify user has write:accounts permission

Cost Explorer Issues

No Cost Data

Symptoms:

• Cost Explorer shows blank
• Dashboard widgets empty
• No historical data

Solutions:

1. Enable AWS Cost Explorer - Must be activated in AWS Billing Console
2. Wait for data - Initial data takes 24-48 hours
3. Check permissions - IAM role needs ce:* permissions
4. Verify account - Cost Explorer must be enabled in management account

Stale Cost Data

Symptoms:

• Data seems outdated
• Yesterday’s costs not showing

Solutions:

• AWS Cost Explorer data has 24-48 hour delay
• This is normal AWS behavior
• Check back the next day for updated data

Automation Issues

Automation Failed

Symptoms:

• Automation Reports show failure
• Error status in Automations page

Solutions:

1. View the specific error in Automation Reports
2. Check IAM Permissions
3. Verify the automation is enabled
4. Check AWS service limits

Automation Not Running

Symptoms:

• No recent executions
• Automation shows enabled but no activity

Solutions:

1. Continuous automations - Should run automatically when enabled
2. Cadence automations - Wait for scheduled run time
3. Trigger automations - Must be manually triggered
4. Check for any system-wide issues

Login Issues

Can’t Log In

Symptoms:

• Login fails
• Error after entering credentials

Solutions:

1. Verify email - Must match registered email
2. Check Cognito - Reset password if needed
3. Clear cache - Try incognito/private window
4. Check status - Verify SkySaver service status

No Access After Login

Symptoms:

• Login succeeds but can’t see features
• Empty dashboard

Solutions:

1. Verify you’re in the correct project (check project selector)
2. Contact admin to verify RBAC permissions
3. Ensure user was added to the project

Performance Issues

Slow Page Load

Symptoms:

• Pages take long to load
• Timeouts

Solutions:

1. Check internet connection
2. Try a different browser
3. Clear browser cache
4. Reduce date range in queries

Reports Timeout

Symptoms:

• Automation reports won’t load
• Export times out

Solutions:

1. Filter to smaller date range
2. Filter by specific automation
3. Try during off-peak hours

Related Topics

• IAM Permissions - AWS permission issues
• FAQ - Frequently asked questions