Alibaba Name / tag not imported for specific resource types

Bug Report Draft
Describe the bug
We are using the Alibaba Cloud integration to fetch resource costs. We have discovered an issue where certain resources are being imported with a blank name and missing tags. However, upon checking the Alibaba Cloud console directly, these specific resources do have names and tags properly assigned to them. The integration seems to be dropping or failing to map this metadata during the fetch process.

To Reproduce
Steps to reproduce the behavior:

Trigger the Alibaba Cloud integration to fetch/import resource cost data.

Navigate to the resource inventory or cost management dashboard in our system.

Search for the affected resources (e.g., cloud_resource_id: d-xxxxxxx).

View the resource details and observe that the name is blank and no tags are associated with the resource.

Expected behavior
The integration should successfully fetch and map the native name and tags from Alibaba Cloud to our system's payload alongside the cost data, ensuring our resource inventory matches the source cloud exactly.

Screenshots
(Please attach a screenshot of the resource in your system showing the blank name/tags, AND a screenshot of the exact same resource in the Alibaba Cloud console showing that the name and tags exist.)

Desktop (please complete the following information):

OS: windows

Browser: Chrome

Version: latest

Additional context
Below is an example of the JSON payload for one of the affected resources (cloud_resource_id: d-xxxxxxx). Notice the absence of name and tags fields at the root or within the meta object:

JSON
[
{
"_first_seen_date": "2026-03-08T00:00:00",
"_last_seen_date": "2026-04-07T00:00:00",
"active": false,
"applied_rules": [
{
"id": "xx-xxx-xxxxx",
"name": "Rule for Alibaba_1770279613",
"pool_id": "8xxxxxxx"
}
],
"cloud_account_id": "xxxxxxxx",
"cloud_account_name": "Alibaba",
"cloud_account_type": "alibaba_cnr",
"cloud_resource_id": "d-xxxxxxx",
"constraint_violated": false,
"cost": 617.472,
"created_at": 1772978440,
"deleted_at": 0,
"employee_id": "xxxxxxx",
"first_seen": 1772928000,
"id": "xxxxxxx",
"is_environment": false,
"last_expense": {
"cost": xxxxx,
"date": xxxxx
},
"last_seen": xxxxxx,
"meta": {
"cloud_console_link": null
}
}
]

Start by reproducing the Alibaba Cloud import for the affected cloud_resource_id and inspect the resource inventory or cost management payload. Compare the imported data with the Alibaba Cloud console, focusing on the resource types that lose metadata. Done means the native name and tags appear in the imported resource payload and match the source resource.

Written by the indexing model from the issue text.