Skip to content

docs: Document futureCall.enabled and futureCall.executionEnabled - #863

Merged
Crazelu merged 8 commits into
serverpod:mainfrom
Crazelu:docs/future-call-config
Sep 25, 2026
Merged

Crazelu merged 8 commits into
serverpod:mainfrom
Crazelu:docs/future-call-config

Conversation

@Crazelu

@Crazelu Crazelu commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

Future call config was updated in #5766 and #5772 to introduce enabled and executionEnabled.

The top-level futureCallExecutionEnabled is now configured using futureCall.executionEnabled. Support for futureCallExecutionEnabled is still maintained for backwards compatibility.

@Crazelu
Crazelu marked this pull request as ready for review September 24, 2026 17:34
@Crazelu
Crazelu requested review from a team September 24, 2026 17:35
Comment thread docs/06-concepts/06-scheduling/05-configuration.md Outdated
Comment thread docs/06-concepts/06-scheduling/05-configuration.md Outdated
Comment thread docs/06-concepts/06-scheduling/05-configuration.md Outdated
Comment thread docs/06-concepts/06-scheduling/05-configuration.md Outdated
Comment thread docs/06-concepts/07-operations/06-scalability.md Outdated
@developerjamiu

Copy link
Copy Markdown
Contributor

Question: the parser still honors the top-level futureCallExecutionEnabled as a fallback, while the PR says "replaces". Worth a line here, or leave it to the upgrade guide for the release that ships this? I'd lean upgrade guide.

Comment thread docs/06-concepts/06-scheduling/05-configuration.md Outdated
@developerjamiu

Copy link
Copy Markdown
Contributor

Nit: an action-shaped title reads better in the changelog, for example "docs: Document futureCall.enabled and futureCall.executionEnabled".

@Crazelu Crazelu changed the title docs: Future call config docs: Document futureCall.enabled and futureCall.executionEnabled Sep 25, 2026
Crazelu and others added 5 commits September 25, 2026 10:39
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
@Crazelu

Crazelu commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator Author

Question: the parser still honors the top-level futureCallExecutionEnabled as a fallback, while the PR says "replaces". Worth a line here, or leave it to the upgrade guide for the release that ships this? I'd lean upgrade guide.

I have updated the description to highlight the backwards compatibility. I also agree with the upgrade guide direction.

@developerjamiu developerjamiu left a comment

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.

LGTM

@Crazelu
Crazelu merged commit 8240ac0 into serverpod:main Sep 25, 2026
5 checks passed
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.

2 participants