Issue Summary

The metric ID displayed on the Statuspage metrics page changes to an incorrect ID after data submission, causing confusion and API call rejections with error code 403.

Steps to Reproduce

• Create a new metric on the Systems metrics page.

• Submit the data source; whenever the metric is added, the page displays the correct metric ID in the "waiting for data" view.

• Once API data is successfully submitted to this metric, the view changes, and the advanced options only show a different Metric ID—one that is incorrect.

• While the original API call with the "old" Metric ID continues to work, updating my API call to the new Metric ID results in the calls being rejected with error code 403 by Statuspage.

Expected Results

The Metric ID should not change.

Actual Results

• While the original API call with the "old" Metric ID continues to work, updating my API call to the new Metric ID results in the calls being rejected with error code 403 by Statuspage.
• This usability issue is quite confusing for developers, as once a metric is populated with data, the original, correct Metric ID cannot be retrieved.

• The only viable workaround is to fetch all metrics via the Statuspage API. The original, hence "correct," Metric ID remains intact.

[ 
{ 
name: 'ABC', 
metric_identifier: null, 
created_at: '2025-07-17T10:59:56.188Z', 
updated_at: '2025-07-17T10:59:56.188Z', 
id: 'xxyyzz', 
metrics_provider_id: 'xxyyzz', 
display: false, 
y_axis_min: null, 
y_axis_max: null, 
y_axis_hidden: false, 
suffix: 'temp', 
decimal_places: 0, 
tooltip_description: null, 
most_recent_data_at: '2025-07-17T11:01:35.000Z', 
backfilled: true 
}

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.