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
Currently, deploying the same workflow across multiple server-based browsers, including those within Docker containers, presents some challenges. Specifically, importing workflows via file uploads is not the most efficient method. Each time, we have to manually download and upload files, which is time-consuming and increases the risk of errors. To address this issue, I propose adding the ability to import workflows directly from the network.
By supporting network imports, users can load and update workflows directly via a URL, significantly improving our efficiency, particularly when rapidly deploying and updating workflows. Additionally, this aligns with modern application practices, providing a smoother and more intuitive user experience.
I hope this feature's feasibility can be evaluated and considered for implementation in future releases. Thank you for your support and understanding.
The text was updated successfully, but these errors were encountered:
Currently, deploying the same workflow across multiple server-based browsers, including those within Docker containers, presents some challenges. Specifically, importing workflows via file uploads is not the most efficient method. Each time, we have to manually download and upload files, which is time-consuming and increases the risk of errors. To address this issue, I propose adding the ability to import workflows directly from the network.
By supporting network imports, users can load and update workflows directly via a URL, significantly improving our efficiency, particularly when rapidly deploying and updating workflows. Additionally, this aligns with modern application practices, providing a smoother and more intuitive user experience.
I hope this feature's feasibility can be evaluated and considered for implementation in future releases. Thank you for your support and understanding.
The text was updated successfully, but these errors were encountered: