cant open workflow specific app after upgrading to 1.1.3

[terrysun1216]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

when open one specific workflow app in the studio browser shows error logs as follows and can't open the app:

NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]
    _collectStartupConditionsTelemetry resource:///modules/BrowserGlue.sys.mjs:1934
    BG__onFirstWindowLoaded resource:///modules/BrowserGlue.sys.mjs:1999
    BG_observe resource:///modules/BrowserGlue.sys.mjs:1202
    _delayedStartup chrome://browser/content/browser-init.js:667
[BrowserGlue.sys.mjs:1940:15](resource:///modules/BrowserGlue.sys.mjs)
    _collectStartupConditionsTelemetry resource:///modules/BrowserGlue.sys.mjs:1940
    BG__onFirstWindowLoaded resource:///modules/BrowserGlue.sys.mjs:1999
    BG_observe resource:///modules/BrowserGlue.sys.mjs:1202
    _delayedStartup chrome://browser/content/browser-init.js:667
Experiment add-an-image-to-pdf-with-alt-text-rollout has unknown featureId: addAnImageInPDF [RemoteSettingsExperimentLoader.sys.mjs:766:21](resource://nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs)
    _validateBranches resource://nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs:766
    checkRecipe resource://nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs:673
Key event not available on some keyboard layouts: key=“z” modifiers=“control,alt” id=“toggleSidebarKb” [browser.xhtml](chrome://browser/content/browser.xhtml)
Key event not available on some keyboard layouts: key=“x” modifiers=“accel,alt” id=“viewGenaiChatSidebarKb” [browser.xhtml](chrome://browser/content/browser.xhtml)
Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode” [browser.xhtml](chrome://browser/content/browser.xhtml)
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” [browser.xhtml](chrome://browser/content/browser.xhtml)
QM_TRY failure (WARNING): 'Unavailable, context dom::quota::FirstInitializationAttempt::TemporaryStorage', file dom/quota/ActorsParent.cpp:1315
QM_TRY failure (WARNING): 'Unavailable, context dom::quota::FirstInitializationAttempt::TemporaryStorage, storage-origin http://localhost', file dom/quota/ActorsParent.cpp:2843

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

The error message "NS_ERROR_NOT_IMPLEMENTED" typically indicates that a certain feature or function is not implemented in the browser or the application. This can sometimes occur due to compatibility issues between the application and the browser version being used.

Here are a few steps you can try to resolve this issue:

1. Browser Compatibility: Ensure that you are using a supported and up-to-date browser. Sometimes, certain features may not be fully supported in older or less common browsers.

2. Clear Cache and Cookies: Try clearing your browser's cache and cookies, as these can sometimes cause unexpected behavior.

3. Check for Browser Extensions: Disable any browser extensions that might interfere with the application's functionality, as they can sometimes cause conflicts.

4. Review Dify Configuration: Double-check your Dify configuration settings to ensure everything is set up correctly, especially after an upgrade.

5. Logs and Debugging: Check the server logs for any additional error messages that might provide more context on the issue.

6. Revert to Previous Version: If the issue persists and is critical, consider reverting to a previous version of Dify that was working correctly, while you investigate further.

If these steps do not resolve the issue, it might be helpful to look for any specific changes in the Dify 1.1.3 release notes or documentation that could affect the workflow app functionality, although I couldn't find specific information on this in the available data.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[terrysun1216]

it shows this console logs when opened in chrome:

[dosubot[bot]]

Hi, @terrysun1216. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• Workflow app fails to open after upgrading to version 1.1.3.
• Error logs suggest issues with browser startup conditions telemetry in a self-hosted Docker environment.
• You provided Chrome console logs for further diagnosis.
• I suggested troubleshooting steps like checking browser compatibility and reviewing configuration settings.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
• If no updates are provided, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!