Hi there, Looks like we are having issues with tiger backend when importing modules using JWT authentication, which seems to be happening after

gd-ai-assistant

release, is there anyone specialist in this area available to help?

Hi Jhonatan, could you please provide more details and clarify what actions you’re taking when you say - importing modules using JWT authentication? Also, please provide more information on the “issues” you’re now facing. If you’re seeing any errors, can you please check your Dev tool in your browser and check for errors there that may help. If you could also provide us with the related TraceID we can try and check our logs for you.

so we import the modules this way:

import(
  `${data['good_data_url']}/components/tigerBackend.js`
  ).then(response => {
    const { default: factory, TigerJwtAuthProvider } = response;

    // {{ workspace }}.js dynamic import
    import(
      `${data['good_data_url']}/components/${data['workspace_id']}.js`
      ).then(response => {
        const { setContext } = response;

        setContext({
            backend: factory()
              .onHostname(data['good_data_url'])
              .withAuthentication(new TigerJwtAuthProvider(data['jwt'])),
            workspaceId: data['workspace_id'],
        });

        iframeListenForJwt(data['jwt']);
    });
});

first import tigerBackend.js and then the specific workspace.js module. and this was working until last week, for more than 1 year, but now suddenly we are getting this error

Uncaught (in promise) NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': this constructor has already been used with this registry

at index.ts:35:23

at examplecompanya.js:46:1283

(examplecompanya is the name of the workspace) and this is the line that is failing

window.customElements.define("gd-ai-assistant", GenAIAssistant);

it seems the JS is trying to define it twice, both in the workspace JS and in the tigerBackend, or something like that.

Thanks for the detailed explanation - We will look into this and get back to you asap with more details.

alright thank you!

Hi @Michael Ullock is this issue related to your announcement below, or a separate issue? https://support.gooddata.com/hc/en-us/articles/42486336068371-Thu-June-26th-2025-Unexpected-GoodData-Cloud-Issue

This seems to be a separate issue based on the timeframe and issue reported - However, this is already with our Tier 2 team and they will get back to you as soon as possible with an update for you. Thanks for your patience in the meantime!

Thanks Michael, please keep us closely posted, as our customers experienced a long outage today because of this, and we need to provide clear answers about the root cause.

We are still looking into that. We will contact you back today.

morning the error is not happening anymore, I am thinking this might have had something to do with the instability or another factor, did you guys change anything on the script so far? We had this script running for more than a year and suddenly it started failing at the same time as the instability, so it's very suspicious that it might have been related.

Hi Jhonatan, thank you for confirming that the error has stopped! It does not relate to the incident we announced, because it affected a different Datacenter than the one in which your org resides. However, there was indeed a separate issue affecting your DC (DUB1) during Thursday that was causing instability in the

gen-ai-service

. I believed this has caused the issues you experienced, and the fact that they are no longer occurring attests to that. Our apologies for the inconvenience, and for the delay in bringing this information to you! But rest assured that the

gen-ai-service

is quite stable now and shouldn’t cause further issues 🙂

thanks for the info Francisco, that is very helpful!

You’re very much welcome. Reach out to us at any time, should you have any more questions or run into any trouble!