Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add import advice to Optimize page #4876

Closed
5 tasks done
toco-cam opened this issue Jan 3, 2025 · 0 comments
Closed
5 tasks done

Add import advice to Optimize page #4876

toco-cam opened this issue Jan 3, 2025 · 0 comments
Assignees
Labels
scope:documentation Changes to the product documentation. scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix. version:optimize 3.11.18 version:optimize 3.12.13 version:optimize 3.13.10 version:optimize 3.14.2 version:optimize 3.15.0

Comments

@toco-cam
Copy link
Member

toco-cam commented Jan 3, 2025

Acceptance Criteria (Required on creation)

  • The information from the C8 Docs is extended by:

A similar problem can occur when the connected engine faces a high load during the initial data import by a new Optimize instance. Please ensure that no data is deleted during this phase. Consider switching off history clean-up.

and added to the C7 Docs

Hints

Requested by a customer - https://jira.camunda.com/browse/SUPPORT-16817

Links

Breakdown

Pull Requests

Preview Give feedback

Dev2QA handover

  • Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:documentation Changes to the product documentation. scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix. version:optimize 3.11.18 version:optimize 3.12.13 version:optimize 3.13.10 version:optimize 3.14.2 version:optimize 3.15.0
Projects
None yet
Development

No branches or pull requests

4 participants