# Troubleshooting
As you use Data Exports or Cost and Usage Reports (CUR), you might encounter certain issues or challenges that require troubleshooting. Use this troubleshooting section for recommendations that help you to resolve common problems quickly and efficiently.
**Topics**
+ [General troubleshooting](troubleshooting-data-exports.md)
+ [Troubleshooting CUR 2.0](troubleshooting-cur-2-0.md)
+ [Troubleshooting the cost and usage dashboard](troubleshooting-dashboard.md)
+ [Troubleshooting Cost and Usage Reports](troubleshooting-cur.md)
+ [Troubleshooting carbon emissions data exports](troubleshooting-carbon-emissions.md)
# General troubleshooting
**Topics**
+ [Why is my export unhealthy?](#dataexports-unhealthy-export)
+ [Why is my SQL statement not being accepted by Data Exports?](#dataexports-sql-statement)
+ [Why can't I locate a predefined SQL script for configuring Athena within Data Exports?](#dataexports-sql-script)
+ [Why is one of my export partitions empty?](#dataexports-empty-partition)
+ [Why are there no report files in the Amazon S3 bucket?](#cur-no-report-files)
## Why is my export unhealthy?
An “unhealthy” export is one that encountered an error when it last tried to deliver a refresh to your Amazon S3 bucket. You may see one of the following error messages when hovering your cursor over the “unhealthy” message or by calling the `GetExport` API.
+ **Data Exports issues**
+ **Insufficient permission:** This means Data Exports was unable to deliver the export files to your S3 bucket. This can be fixed by updating your S3 bucket policy with the permission listed in [Setting up an Amazon S3 bucket for data exports](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-s3-bucket.html).
+ **Bill owner changed:** This error can occur when your AWS account moves to a new organization or leaves an organization in AWS Organizations. It can also happen when you're in an organization and your management account changes whether you belong to a billing group in AWS Billing Conductor. The best way to solve this problem is to create a new CUR and delete your old CUR. If you believe your account should not have changed organizations or billing groups, contact your account admin.
+ **Internal failure:** This error is due to an issue with the Data Exports internal infrastructure. Review the AWS Service Health Dashboard for updates on any service-wide issues that may be affecting Data Exports, or contact AWS Support for more information or help.
+ **QuickSight integration issues**
+ **Insufficient SPICE capacity:** This error means that QuickSight does not have enough processing capacity provisioned to ingest your cost and usage data. For information on how to increase your SPICE capacity, see [Managing SPICE memory capacity](https://docs.aws.amazon.com/quicksight/latest/user/managing-spice-capacity.html).
+ **Insufficient permission to access the manifest file:** The service role you assigned to QuickSight to access your S3 bucket is no longer working. Review your service policy to make sure it's giving read permissions to the S3 bucket storing your cost and usage data.
+ **Access denied when trying to access manifest file:** Your IAM role does not have access to the S3 bucket storing your export files to check whether a QuickSight dashboard exists for this export. The dashboard may or may not be working. You need `s3:GetObject` permissions on the S3 bucket storing the export data in order to be able to check for a QuickSight dashboard.
+ **QuickSight CreateBundle failed:** This error means your dashboard failed to be created in QuickSight. This may have happened due to a delay in IAM role propagation if you created a new service role, or if you selected an existing service role that did not have the right permissions. Use the retry action if you created a new service role. If you selected an existing service role, you should delete your export and create a new one with a new service role.
+ **Dashboard does not exist:** This error means your dashboard was deleted in QuickSight. You should delete your existing cost and usage dashboard export in Data Exports and recreate it.
+ **QuickSight account does not exist:** This error means your QuickSight account was deleted. You will need to recreate your QuickSight account to use a dashboard again. After recreating your QuickSight account, you should delete your existing cost and usage dashboard export in Data Exports and recreate it.
## Why is my SQL statement not being accepted by Data Exports?
Data Exports supports a limited set of SQL syntax that is mainly focused on column selections and row filters. Make sure your SQL statement is using only the relevant keywords and operators. For full details, see [Data query](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-data-query.html).
## Why can't I locate a predefined SQL script for configuring Athena within Data Exports?
Unlike Cost and Usage Reports (CUR), Data Exports doesn't offer an SQL file for setting up Athena to query your exports. You'll need to either use a CloudFormation template for Data Exports or manually configure Athena. For more information, see [Configuring Amazon Athena](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-processing.html).
## Why is one of my export partitions empty?
If an export is larger than most applications can handle, AWS splits the report into multiple files. If an export update is smaller than the previous export and you're using “overwrite” mode, AWS overwrites the unneeded partitions with empty data. The export manifest only lists the partitions that have data. Review the report’s manifest file to find any empty files that you don’t need to ingest.
## Why are there no report files in the Amazon S3 bucket?
Confirm that the Amazon S3 bucket policy grants the **billingreports.amazonaws.com** service permission to put files in the bucket. For more information on the required bucket policy, see [Setting up an Amazon S3 bucket for data exports](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-s3-bucket.html) or [Setting up an Amazon S3 bucket for Cost and Usage Reports](https://docs.aws.amazon.com/cur/latest/userguide/cur-s3.html).
# Troubleshooting CUR 2.0
**Topics**
+ [Why are some columns that were available in CUR not appearing in CUR 2.0?](#dataexports-missing-columns)
+ [What will happen to legacy Cost and Usage Reports; will it be deprecated?](#dataexports-legacy-cur-deprecation)
+ [Does creating an export of CUR 2.0 affect my legacy CUR?](#dataexports-legacy-cur-affect)
+ [Why can’t I create an export of CUR 2.0 even though I have IAM permissions to use Data Exports and the CUR table?](#dataexports-missing-iam-permissions)
+ [When attempting to create a data export with the same CSV format as the legacy CUR columns, I get an "Invalid QueryStatement" error. How can I resolve this?](#dataexports-invalid-query-statement)
+ [After migrating to Data Exports CUR 2.0, can I have a legacy CUR export and a CUR 2.0 export at the same time?](#dataexports-revert)
+ [When attempting to create an export of CUR 2.0, I get the error "This account is unable to create an export against this table". Why can't I create a CUR 2.0 export?](#dataexports-pro-forma)
## Why are some columns that were available in CUR not appearing in CUR 2.0?
In CUR 2.0, four column types became nested into four individual columns. The resulting nested columns are: `product`, `discount`, `resource_tag`, and `cost_category`.
In legacy CUR, there could be hundreds of columns with names that started with these strings. The variations depended on customer usage of AWS services or agreements with AWS. This schema design resulted in hundreds of columns that were often sparsely filled. The variability of the columns could also cause problems with SQL queries due to a charging schema.
As a result, the columns that could vary across different AWS columns were nested together into these four columns. Certain product columns that are commonly used were not nested.
You can recreate the schema of the CUR in your CUR 2.0 export by using the dot operator in SQL. To learn how to do this, see [Migrating from CUR to Data Exports CUR 2.0](https://docs.aws.amazon.com/cur/latest/userguide/data-exports-migrate.html).
## What will happen to legacy Cost and Usage Reports; will it be deprecated?
We currently have no plans to deprecate legacy CUR. However, as CUR 2.0 in Data Exports offers several improvements such as a consistent schema, nested data, and additional columns (`bill_payer_account_name` and `line_item_usage_account_name`), we recommend migrating to CUR 2.0.
While there is no target date, we are planning to eventually deprecate **Cost and Usage Reports** under **Legacy Pages** in the console. However, all of the same functionality to create, update, and delete legacy CUR is available through the **Data Exports** console page.
**Note**
Detailed Billing Reports (DBR), another legacy billing feature, may be deprecated at a later date. The feature has been unavailable for new customers since July 8, 2019.
## Does creating an export of CUR 2.0 affect my legacy CUR?
CUR and CUR 2.0 are two distinct reports. When creating CUR 2.0, there is no impact on your existing CUR settings. You can choose between legacy CUR and CUR 2.0 based on your preferences.
## Why can’t I create an export of CUR 2.0 even though I have IAM permissions to use Data Exports and the CUR table?
Make sure you also have IAM permissions for `cur:PutReportDefinition`.
## When attempting to create a data export with the same CSV format as the legacy CUR columns, I get an "Invalid QueryStatement" error. How can I resolve this?
Currently, you can't rename your columns to have special characters such as "/" to match the legacy CUR column names in CSV format. For information about the supported character types, see [SQL query](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-data-query.html#dataexports-sql-query).
## After migrating to Data Exports CUR 2.0, can I have a legacy CUR export and a CUR 2.0 export at the same time?
Yes, you can have up to 10 legacy CUR exports and 5 CUR 2.0 exports at the same time.
## When attempting to create an export of CUR 2.0, I get the error "This account is unable to create an export against this table". Why can't I create a CUR 2.0 export?
Unlike legacy CUR, CUR 2.0 does not currently support creating an export of CUR 2.0 with pro forma billing data. If you are part of a billing group in AWS Billing Conductor, you are only allowed to receive pro forma billing data. As a result, you receive this error message when trying to create an export of CUR 2.0. You can still create a legacy CUR export.
# Troubleshooting the cost and usage dashboard
**Topics**
+ [Why did my cost and usage dashboard export fail right after I created it?](#dataexports-failed-export)
+ [Why can't I access the dashboard?](#dataexports-dashboard-access)
+ [Why am I being taken to the console admin page to unsubscribe the QuickSight account when I try to view the dashboard?](#dataexports-quicksight-unsubscribe)
+ [Why don't I see any data in the cost and usage dashboard that I just created?](#dataexports-current-month-data)
+ [Why can't I see historical data in the cost and usage dashboard?](#dataexports-historical-data)
+ [Why did my QuickSight dashboard link disappear from the Data Exports console page?](#dataexports-qs-dashboard-link)
+ [How can I configure Amazon QuickSight to visualize resource tags in CUR 2.0?](#dataexports-qs-configure)
## Why did my cost and usage dashboard export fail right after I created it?
Your cost and usage dashboard export may have failed due to a delay in IAM role propagation. If you created a new service role for this export, Amazon QuickSight may not have had permission to access your S3 bucket and create your dashboard. When you see the error “Insufficient permission to access the manifest file” in the Export status, choose Export, and then choose Retry in the table action menu.
If you didn’t create a new service role for your cost and usage dashboard export, you may have specified an incorrect service role for QuickSight to use. In this case, you should delete your export and recreate it, while also creating a new service role in the cost and usage dashboard console workflow.
## Why can't I access the dashboard?
You may not be able to access the cost and usage dashboard in Amazon QuickSight if you don’t have permission to view it. To troubleshoot, open your export by choosing the export name. Check the QuickSight created by field to see who created the dashboard. Ask the user to give you permission to view the dashboard.
## Why am I being taken to the console admin page to unsubscribe the QuickSight account when I try to view the dashboard?
You may encounter this error if you're using the “Active directory” authentication method. Choose the cost and usage dashboard export name to view the details of your export. Choose **QUICKSIGHT SIGN IN** to sign in to your QuickSight account. You'll be able to see the dashboard if you have permission to view it.
## Why don't I see any data in the cost and usage dashboard that I just created?
Your cost and usage dashboard could be missing the data for the current month because it can take up to 24 hours for all your data to be populated in your dashboard. Check the status of your cost and usage dashboard export. If the export status says “Healthy”, allow 24 hours for your dashboard to update with the current month's data. If you don’t see the current month's data in your dashboard after 24 hours, contact AWS Support. You can check the creation time of your cost and usage dashboard in the Exports and Dashboards table on the Data Exports console page.
## Why can't I see historical data in the cost and usage dashboard?
Your cost and usage dashboard might be missing the six months of historical data for any of the following reasons:
+ **No historical data exists:** If you have an account without six months of historical spending due to being a new account or recently changing membership in AWS Organizations, no historical data can populate the dashboard.
+ **Historical backfill is still in progress:** Historical data backfill by Data Exports can take up to 24 hours to complete. You can use the SDK/CLI to check if any backfill executions failed with the `ListExecutions` API for this export, or if they are still in progress. Wait a little longer or use `ListExecutions` to ensure the backfill is not in progress.
+ **Historical backfill failed:** Historical data backfill may have failed to complete due to an internal error. You can come to this conclusion if it's been more than 24 hours and the backfill is not complete, or you can use the `ListExecutions` API in the SDK/CLI and look for any failed executions for this export. If you believe the backfill has failed, try remaking the cost and usage dashboard in the console. If it fails a second time, we recommend reaching out to AWS Support.
## Why did my QuickSight dashboard link disappear from the Data Exports console page?
The Data Exports console page reads from a file in your S3 bucket in order to identify the QuickSight dashboard that the export is linked to. If this file is altered or deleted, the console doesn't know that a dashboard exists for this export. While your dashboard still exists in QuickSight, you'll need to repair this file for the link to reappear.
## How can I configure Amazon QuickSight to visualize resource tags in CUR 2.0?
The cost and usage dashboard feature does not support visualizing resource tags. However, you can still receive your resource tag data in the CUR 2.0 export. If you want an AWS supported QuickSight dashboard for visualizing your cost and usage with tags, refer to the [CUDOS Dashboard from AWS Well-Architected Labs](https://catalog.workshops.aws/awscid/en-US/dashboards/foundational/cudos-cid-kpi/#cudos-dashboard). It currently only uses data from legacy CUR, but will support CUR 2.0 in the future.
# Troubleshooting Cost and Usage Reports
**Topics**
+ [Why does my Cost and Usage Report data not match the data shown in other Billing and Cost Management features?](#cur-data-differences)
+ [How can I backfill data after changing my report settings?](#cur-backfill-data)
+ [Why is my report file folder in Amazon S3 stored in an unnamed folder?](#cur-unnamed-folder)
+ [Why can’t I select the option to include resource IDs on my report?](#cur-activate-resource-ids)
+ [Why don't my Cost and Usage Report queries for Amazon Athena work on Amazon Redshift, or my Amazon Redshift queries on Amazon Athena?](#cur-athena-redshift-queries)
+ [Why have the columns included in my report changed from a previous month](#cur-cur-columns-changed)
+ [Why don't my queries or tables work after the columns in my report changed?](#cur-cur-columns-changed-solutions)
+ [How do I query my report?](#cur-cur-query-help)
+ [Where can I find the billing data for my Amazon EC2 Dedicated Host?](#cur-cur-dedicated-hosts)
+ [How do I interpret the billing data for my Amazon EC2 Elastic IP addresses?](#cur-cur-elastic-ips)
+ [How do unblended and blended rates or costs differ in consolidated billing?](#cur-consolidated-billing-unblended-blended)
+ [Why do some line items in my report have a blended rate or blended cost of 0?](#cur-blended-rate-zero)
+ [How are All Upfront Reserved Instances amortized in my report?](#cur-all-upfront-ri)
## Why does my Cost and Usage Report data not match the data shown in other Billing and Cost Management features?
Other Billing and Cost Management features (Cost Explorer, Detailed Billing Reports, Billing and Cost Management console) might present your costs differently for the following reasons:
+ The billing features round cost data in different ways.
+ The billing features might have different data refresh settings. For example, you can choose whether or not your Cost and Usage Report automatically refreshes a previously closed bill with any refunds, credits, or Support fees applied after the bill is finalized. Cost Explorer automatically reflects the same items. In this scenario, if you don’t activate the automatic refresh on your Cost and Usage Report, then the Cost and Usage Report data won’t match the Cost Explorer data.
+ The billing features can group charges differently. For example, the **Bills** page in the Billing and Cost Management console shows data transfer charges as a separate **Data Transfer** grouping within your **AWS Service Charges**. Meanwhile, Cost and Usage Reports and Cost Explorer show data transfer charges as a usage type for each service.
If after reviewing these reasons you still believe you're seeing discrepancies between your Cost and Usage Report and other Billing and Cost Management features, open a support case to request a review of your cost data. In your support case, make sure to provide the report name and the billing period that you would like reviewed. For more information on opening a case, see [Getting help with your exports and reports](billing-get-answers.md).
## How can I backfill data after changing my report settings?
Open a support case to request a backfill of your cost data. In your support case, make sure to provide the report name and the billing period that you want backfilled. For more information on opening a case, see [Getting help with your exports and reports](billing-get-answers.md).
Note that you can't get a backfill of cost data for the following scenarios:
+ You can't get a backfill for cost data from before the date that you created the account.
+ If you use AWS Organizations and the structure of your organization changed, such as which account is designated the management account, then you can't get a backfill of data with the previous organization structure.
+ If you use AWS Organizations and you change organizations, then you can't get a backfill of data from prior to joining your current organization.
## Why is my report file folder in Amazon S3 stored in an unnamed folder?
Any **/** character in the **Report path prefix** of your report generates an unnamed folder in your Amazon S3 bucket. To remove the unnamed folder in your next report update, edit your report settings and remove the **/** character from the **Report path prefix**. For instructions, see [Editing your Cost and Usage Reports configuration](edit-cur.md).
## Why can’t I select the option to include resource IDs on my report?
When you create your report, you can select the option to **Include resource ID**. If you create your report with **Report versioning** set to **Overwrite existing report**, then you can’t modify your **Include resource ID** selection after you create your report. To include resource IDs, you must create a new report and select the **Include resource ID** option.
## Why don't my Cost and Usage Report queries for Amazon Athena work on Amazon Redshift, or my Amazon Redshift queries on Amazon Athena?
Amazon Athena and Amazon Redshift databases format Cost and Usage Report columns differently. Amazon Athena adds an underscore between words in the column name (line\$1item\$1normalized\$1usage\$1amount). Amazon Redshift adds an underscore between the column type and the attribute (lineitem\$1normalizedusageamount). Make sure to modify your queries to match the column name format in Amazon Athena or Amazon Redshift.
## Why have the columns included in my report changed from a previous month
The columns that AWS includes in your report depend on your AWS usage. Every report includes columns with the **identity/**, **bill/**, and **lineItem/** prefixes:
+ identity/LineItemId
+ identity/TimeInterval
+ bill/InvoiceId
+ bill/BillingEntity
+ bill/BillType
+ bill/PayerAccountId
+ bill/BillingPeriodStartDate
+ bill/BillingPeriodEndDate
+ lineItem/UsageAccountId
+ lineItem/LineItemType
+ lineItem/UsageStartDate
+ lineItem/UsageEndDate
+ lineItem/ProductCode
+ lineItem/UsageType
+ lineItem/Operation
+ lineItem/AvailabilityZone
+ lineItem/ResourceId
+ lineItem/UsageAmount
+ lineItem/NormalizationFactor
+ lineItem/NormalizedUsageAmount
+ lineItem/CurrencyCode
+ lineItem/UnblendedRate
+ lineItem/UnblendedCost
+ lineItem/BlendedRate
+ lineItem/BlendedCost
+ lineItem/LineItemDescription
+ lineItem/TaxType
+ lineItem/LegalEntity
All other columns are included only if your monthly AWS usage generates data to populate those columns.
For example, your report includes **savingsPlan/** columns only if you used Savings Plans during that month.
## Why don't my queries or tables work after the columns in my report changed?
The columns that AWS includes in your report depend on your AWS usage for the month. Because the columns included in your report can change, it’s a best practice to reference column names instead of column numbers in any custom queries or tables based on your report.
## How do I query my report?
For detailed information about querying your Cost and Usage Report, see [CUR Query Library Help](https://wellarchitectedlabs.com/cost/300_labs/300_cur_queries/query_help/) in the AWS Well-Architected Labs website.
## Where can I find the billing data for my Amazon EC2 Dedicated Host?
In the **ResourceID** column, look for the Dedicated Host ID rather than the instance ID. Because Dedicated Hosts are metered by Dedicated Host running hours, your report shows Dedicated Host usage by metered hours associated with the host ID.
## How do I interpret the billing data for my Amazon EC2 Elastic IP addresses?
Amazon EC2 Elastic IP addresses are metered in aggregate. This means that each line item in your report doesn’t correspond with an individual Elastic IP address. Each line item represents the total number of chargeable hours. You can have one Elastic IP address assigned to a running instance at no charge. You’re charged per hour on a pro-rata basis for each additional Elastic IP address that you assign to the instance. Additionally, AWS charges an hourly fee for unassigned Elastic IP addresses.
## How do unblended and blended rates or costs differ in consolidated billing?
With consolidated billing for AWS Organizations, unblended and blended rates or costs can help you understand how much an account's usage would cost for a standalone account versus a linked account in an organization. Some services offer pricing tiers that can lower unit costs as usage increases. Because AWS aggregates all usage for a service in an organization, individual accounts might access lower-priced tiers sooner when their usage is aggregated in an organization's monthly usage.
Unblended rates are the rates associated with an individual account's service usage. For a line item, the unblended cost is usage multiplied by the unblended rate. The unblended cost would be the cost of the account's usage if it were a standalone account. Blended rates are the rates associated with total usage in an organization averaged across accounts. For a line item, the blended cost is usage multiplied by the blended rate. The blended cost is the cost attributed to the account's usage as a linked account in an organization.
For more information and examples of calculating unblended and blended costs, see [Understanding Consolidated Bills](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/con-bill-blended-rates.html) in the *AWS Billing User Guide*
## Why do some line items in my report have a blended rate or blended cost of 0?
Amazon EC2 line items with a Reserved Instance discount have an blended rate of zero. For these line items, the **LineItemType** is **Discounted Usage**.
The blended cost is the usage multiplied by the blended rate. If the value for blended rate or usage is zero, then the blended cost is also zero.
## How are All Upfront Reserved Instances amortized in my report?
Because All Upfront Reserved Instances are paid in full upfront, the amortized costs are reflected in your report as the upfront payment divided over the associated time period (one year or three years).
**reservation/AmortizedUpfrontCostForUsage** and **reservation/EffectiveCost** are the same rate for All Upfront Reserved Instances. This is because both columns are an equal division of the upfront payment for the Reserved Instance over the total hours of its term.
It's expected that your report has **RIFee** line items populated for All Upfront Reserved Instances, even though the **RIFee** is \$10.00. These line items represent the recurring hourly costs for the month, and they have additional usage data in other columns. All Reserved Instances generate **RIFee** line items.
# Troubleshooting carbon emissions data exports
**Topics**
+ [Why can't I create an export of the Carbon emissions table even though I have IAM permissions to use Data Exports and the CUR 2.0 table?](#carbon-emissions-permissions)
+ [Why can't I see carbon emissions data for some member accounts in my organization?](#carbon-emissions-data)
+ [Why is one of the files in my S3 bucket empty?](#carbon-emissions-empty-file)
+ [Why does my S3 export show zero carbon emissions for some Regions and services when there is usage data?](#carbon-emissions-show-zero)
+ [Is historical data backfill available in Data Exports for carbon emissions?](#carbon-emissions-historical-data-backfill)
+ [How can I backfill data after changing my report settings or when a new methodology is released?](#carbon-emissions-backfill-request)
+ [Why can't I see historical data in my S3 bucket?](#carbon-emissions-historical-data)
+ [Why don't I see the newly released columns in my export?](#carbon-emissions-new-columns)
+ [Why is my data not provided using older methodology versions?](#carbon-emissions-methodology)
## Why can't I create an export of the Carbon emissions table even though I have IAM permissions to use Data Exports and the CUR 2.0 table?
To access carbon footprint data, you need the IAM permission `sustainability:GetCarbonFootprintSummary`.
## Why can't I see carbon emissions data for some member accounts in my organization?
If you're using a management (payer) account, you should automatically see carbon emissions data for your management account and all member (usage) accounts in the Carbon emissions table. No extra configuration is required.
However, there is a data lag of up to 21 days for carbon emissions data. For new member accounts, data won't appear in the management account’s carbon emissions data export until the export period that includes when the member account joined the organization. For example, if you linked a new member account in January, its data first appears in the February export.
Similarly, when a member account leaves the organization, its data continues to appear until the export period when it was removed.
## Why is one of the files in my S3 bucket empty?
If your account doesn't have carbon emissions data for a given month, you'll receive a file in your S3 bucket for the given carbon model version and usage period, but the file will be empty.
## Why does my S3 export show zero carbon emissions for some Regions and services when there is usage data?
If your total carbon emissions show as zero, it means they are lower than 0.0000005 MTCO2e, which is our display threshold.
## Is historical data backfill available in Data Exports for carbon emissions?
Yes, upon creating an export you will receive data going back up to January 2022 with the first delivery and one month of data each month thereafter. If your account was created after January 2022, you’ll receive carbon emissions estimates from your account creation date onward.
If you have an existing data export, you can request a backfill. See how in the question below.
## How can I backfill data after changing my report settings or when a new methodology is released?
Open a support case to request a backfill of your carbon data. In your support case, make sure to provide the report name and the start date for your backfill. For more information on opening a case, see [Getting help with your exports and reports](https://docs.aws.amazon.com/cur/latest/userguide/billing-get-answers.html).
Note that you can't get a backfill of carbon data for the following scenarios:
+ You can't get a backfill for carbon data from before the date that you created the account.
+ If you use AWS Organizations and the structure of your organization changed, such as which account is designated the management account, then you can't get a backfill of data with the previous organization structure.
+ If you use AWS Organizations and you change organizations, then you can't get a backfill of data from prior to joining your current organization
## Why can't I see historical data in my S3 bucket?
Your S3 bucket might be missing historical data for any of the following reasons:
+ **No historical data exists:** If you have an account without historical carbon emissions estimates due to being a new account or recently changing membership in AWS Organizations, no historical data can be populated in your S3 bucket. If your account has been created after January 2022, you'll receive the carbon emissions estimates for the entire duration of your account being active.
+ **Historical backfill is still in progress:** Historical data backfill by Data Exports can take up to 24 hours to complete. You can use the SDK/CLI to check if any backfill executions failed with the `ListExecutions` API for this export, or if they are still in progress. Wait a little longer or use `ListExecutions` to ensure the backfill is not in progress.
+ **Historical backfill failed:** Historical data backfill may have failed to complete due to an internal error. You can come to this conclusion if it's been more than 24 hours and the backfill is not complete, or you can use the `ListExecutions` API in the SDK/CLI and look for any failed executions for this export. If you believe the backfill has failed, try creating a new export. If it fails a second time, we recommend reaching out to AWS Support.
## Why don't I see the newly released columns in my export?
Existing exports continue with their original configuration and monthly updates until updated. To add new columns to an existing export, you must update your export configuration for future monthly exports (previously exported data remains unchanged). To backfill data with the new columns, you need to create a new export. This provides up to 38 months of historical data plus monthly updates.
## Why is my data not provided using older methodology versions?
We publish data using the latest methodology version to ensure your estimated emissions are as accurate as possible. If you had an existing data export with data from previous versions, the data will continue to be available for you to reference, unless you delete it. There is no other way to retrieve old versions.
If you configured your Data Export’s *File versioning* to *Overwrite*, we will only update your files if a data improvement is delivered within the same methodology version. If you want to keep all historical versions of your data, select *Create new* under *File versioning*. This will ensure your data is never overwritten.