Handle large Confluence workflows #4214
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flvndvd
commented
Mar 8, 2024
| localLogger.info("Found Confluence top-level pages in space.", { | ||
| topLevelPagesCount: childPageIds.length, | ||
| }); | ||
| localLogger.info( |
philipperolet
approved these changes
Mar 8, 2024
| @@ -39,6 +40,8 @@ const { | |||
| startToCloseTimeout: "20 minutes", | |||
| }); | |||
|
|
|||
| const MAX_HISTORY_LENGTH = 30_000; | |||
There was a problem hiding this comment.
nit: TEMPORAL_WORKFLOW_MAX...
with com explaining for the future noob why this is there (a single confluence workflow may visit more than X pages, this breaks...)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses a problem where certain Confluence connectors exceed the maximum allowed size for Temporal workflows. Currently, the maximum workflow history size is approximately 50,000 events. To prevent reaching this limit and potentially causing issues, this PR introduces a mechanism to continue the workflow in a new instance once the history size reaches 30,000 events.
Risk
Deploy Plan