Skip to content

faq and misc updates#4402

Merged
brianmacdonald-temporal merged 11 commits intomainfrom
auto-migrate-update-08-04
Apr 14, 2026
Merged

faq and misc updates#4402
brianmacdonald-temporal merged 11 commits intomainfrom
auto-migrate-update-08-04

Conversation

@dspinhirne-temporal
Copy link
Copy Markdown
Contributor

@dspinhirne-temporal dspinhirne-temporal commented Apr 8, 2026

What does this PR do?

Updates to FAQ + some misc corrections.

┆Attachments: EDU-6175 faq and misc updates

@dspinhirne-temporal dspinhirne-temporal requested a review from a team as a code owner April 8, 2026 15:16
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Apr 14, 2026 10:04pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

📖 Docs PR preview links


## Frequently asked questions

### When should I opt for auto migration?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think the answer here addresses this question.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LMK if this is more clear.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I may suggest -- the question looks for specific guidance. The current answer just includes points to consider. You could phrase it like this:
The answer depends on your specific situation. However, auto migration is most likely to help if any of the following apply to you:

  • You need to migrate Workers to both self-hosted and Cloud environments simultaneously.
  • You have many long-running Workflows.
  • You have many closed Workflows.
  • You need to migrate Schedules.
    In contrast, auto migration may not be the best solution if you do not have the required components already set up. If your self-hosted clusters do not meet the minimum requirements, you may need to upgrade them before starting the migration. See the section on limitations for more information.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we have a winner. simpler wording ftw.


### I have a long retention period for my Workflows. Is this compatible with Temporal Cloud?

Occasionally, self-hosted [retention periods](/temporal-service/temporal-server#retention-period) are in excess of what
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we ever spell out the max retention period we support for migrations?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it is the same limit as in cloud (90 days). My understanding is that we don't migrate anything older than that. Will let eng. confirm.

Copy link
Copy Markdown
Contributor

@brianmacdonald-temporal brianmacdonald-temporal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few small copyedits, and I weighed in on one of the FAQ questions.


## Frequently asked questions

### When should I opt for auto migration?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I may suggest -- the question looks for specific guidance. The current answer just includes points to consider. You could phrase it like this:
The answer depends on your specific situation. However, auto migration is most likely to help if any of the following apply to you:

  • You need to migrate Workers to both self-hosted and Cloud environments simultaneously.
  • You have many long-running Workflows.
  • You have many closed Workflows.
  • You need to migrate Schedules.
    In contrast, auto migration may not be the best solution if you do not have the required components already set up. If your self-hosted clusters do not meet the minimum requirements, you may need to upgrade them before starting the migration. See the section on limitations for more information.

@lukeknep
Copy link
Copy Markdown
Contributor

LGTM

@brianmacdonald-temporal brianmacdonald-temporal merged commit 299f2c2 into main Apr 14, 2026
10 checks passed
@brianmacdonald-temporal brianmacdonald-temporal deleted the auto-migrate-update-08-04 branch April 14, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants