You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LogRocket is being loaded twice in your application, leading to a session quota exceeded error.
👟 Reproduction steps
Navigate to the Get Started page
Navigate to the Workflows page
The bug: build.umd.js:3103 LogRocket has already been loaded, loading a second instance is not supported. This is often caused by loading LogRocket as a package in your application and as a script tag.
👍 Expected behavior
provide the fix so the warning is not printed in the console
👎 Actual Behavior with Screenshots
is shown in the console.
Novu version
novu Saas
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
The exact problem is that LogRocket is being loaded and initialized twice in your application, which is not supported, and the session quota for LogRocket has been exceeded.
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
LogRocket is being loaded twice in your application, leading to a session quota exceeded error.
👟 Reproduction steps
build.umd.js:3103 LogRocket has already been loaded, loading a second instance is not supported. This is often caused by loading LogRocket as a package in your application and as a script tag.
👍 Expected behavior
provide the fix so the warning is not printed in the console
👎 Actual Behavior with Screenshots
is shown in the console.
Novu version
novu Saas
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
The exact problem is that LogRocket is being loaded and initialized twice in your application, which is not supported, and the session quota for LogRocket has been exceeded.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: