microsoft / ARI

Azure Resource Inventory - It's a Powerful tool to create EXCEL inventory from Azure Resources with low effort
MIT License
1.12k stars 397 forks source link

Skip Token Issue #201

Closed mbcyclotron closed 4 months ago

mbcyclotron commented 4 months ago

Hello -

I am receiving the following error when trying to run the script. I've been unable to find any similar error through general searching and research.

ERROR: { "code": "BadRequest", "message": "Please provide below info when asking for support: timestamp = 2024-07-08T18:00:08.1462571Z, correlationId = 43f5a0a5-fbf1-40f1-a726-f87f3ec9e1d4.", "details": [ { "code": "CouldNotDecodeSkipToken", "message": "Skip token could not be decoded."

aleksei-74 commented 4 months ago

Hello, Same error for me.

code2exe commented 4 months ago

@Claudio-Merola I am having the same errors

ERROR: {ventory [3% Complete.                                                ]
    "code": "BadRequest",
    "message": "Please provide below info when asking for support: timestamp = 2024-07-10T07:24:06.7335216Z, correlationId = 13458ad1-8c5a-4bcf-adc9-096e714e38fe.",
    "details": [
        {
            "code": "CouldNotDecodeSkipToken",
            "message": "Skip token could not be decoded."
        }
    ]
}
ERROR: {
    "code": "BadRequest",
    "message": "Please provide below info when asking for support: timestamp = 2024-07-10T07:24:08.3106135Z, correlationId = dcf7ddcf-29b6-4050-8f31-a6736544d220.",
    "details": [
        {
            "code": "CouldNotDecodeSkipToken",
            "message": "Skip token could not be decoded."
        }
    ]
}
ERROR: {
    "code": "BadRequest",
    "message": "Please provide below info when asking for support: timestamp = 2024-07-10T07:24:09.8610084Z, correlationId = a6bb4556-0193-483c-ae6f-749f7dc6bfd3.",
    "details": [
        {
            "code": "CouldNotDecodeSkipToken",
            "message": "Skip token could not be decoded."
        }
    ]
}

Client: MacOS & WIndows azure cli version: 2.62.0

Please assist.

Thanks for your kind support

Claudio-Merola commented 4 months ago

Hello,

Yea, it was a bug in version 3.1.33, should be fixed now. Can you give a try at version 3.1.34?

mbcyclotron commented 4 months ago

The issue has been resolved in 3.1.34. Thanks.