Multiple versions of our workload in same tenant causing issues?

[box-turtle]

We just deployed two new nupkg workload definitions to our tenant but we cannot create new items for either one.

They point at separate app registrations, and the app registrations have different audiences/resource ids. They also have different workload names.

Our item type is defined like this:

const itemType = `${process.env.WORKLOAD_NAME}.Notebook`;

So since workload name is different in each, itemType is different in each, but the term Notebook is the sam in both. Can that cause a problem?

We also have different "Product" names in both. It is unclear to me how the "Product" is used. Does product = experience?
When I filter items in a workspace I see I can item types like "AI Unlimited Notebook" - how does that mapping to Org.Teradata.Notebook take place?

staging:

WORKLOAD_NAME=Org.Teradata
WORKLOAD_BE_URL=https://session-manager.nonprod.aiunlimited.teracloud.ninja/v1
WORKLOAD_FE_URL=https://feserver.nonprod.aiunlimited.teracloud.ninja
ENV_NAME=staging
VERSION=1.0.7
APP_ID=45f3da91-fda8-42ff-9f1e-b06ce9b2c2cd
RESOURCE_ID=https://nonprod.aiunlimited.teracloud.ninja/feserver/session-manager/Org.Teradata/preview

test:

WORKLOAD_NAME=Org.TeradataTest
WORKLOAD_BE_URL=https://session-manager-test.nonprod.aiunlimited.teracloud.ninja/v1
WORKLOAD_FE_URL=https://feserver-test.nonprod.aiunlimited.teracloud.ninja
ENV_NAME=test
VERSION=1.0.5
APP_ID=4d83e30c-7ccc-4991-9911-bc9a11df3ccc
RESOURCE_ID=https://nonprod.aiunlimited.teracloud.ninja/feserver-test/session-manager-test/Org.TeradataTest

The staging env is using an app registration we have used successfully in the past, test env has a new app registration with same permissions defined.

However new item creation fails on both env with this error:

{
    "error": {
        "code": "UnknownError",
        "pbi.error": {
            "code": "UnknownError",
            "parameters": {},
            "details": []
        }
    }
}

and no call is seen in the logs for our BE servers, so I assume it is failing inside Fabric. I'm trying to figure out how to debug this.

Can someone take a look at these two requestIds and let us know if there is any detail to be gleaned from your logs?

staging requestId: ddfdcba5-5675-fa53-3220-106bd48c06e2

test requestId: 55f71af1-d6d8-6c16-6818-2da75beffd77

[box-turtle]

OK got these fixed. Seems to have been permissions issue on the app registrations.