Skip to content

Conversation

@feiyang3cat
Copy link
Contributor

@feiyang3cat feiyang3cat commented Jan 21, 2026

What changed?

block end users using internal per-ns workers (workflows/activities) , pls note internal sys-ns related are not impacted

strategies:
(1) block by queue names in general-purpose APIs to create workflows, and let the usage of legal dedicated APIs pass
(2) activities and child workflows can be scheduled on internal per-ns queues only if the wrapping workflow runs on this queue

details for workflows:

Workflow Entry Point Access Level Should Adapt?
StartWorkflowExecution Public API Yes — Done
SignalWithStartWorkflowExecution Public API Yes — Done
ExecuteMultiOperation Public API Yes — Done
Start Child Workflow From Workflow Yes —> check parent workflow task queue
Continue-As-New From Workflow No — Inherits parent
Schedules Public API Yes — Done
Cron Public API Yes — Done, covered thru StartWorkflowExecution
Retry Automatic No — Inherits original workflow
ImportWorkflowExecution Admin API No — Admin-only; used for replication
StartAdminBatchOperation Admin API No — Used to start system batch workflows
Nexus StartOperation/Standalone Activity Public API Yes — not for this pr , syncing related team
Worker Deployment Internal No — Allowed
StartBatchOperation Public API for dedicated purpose No — Allowed

details for activities:

  • ScheduleActivity -> covered
  • StandaloneActivity -> not for this pr, syncing related team

Why?

enhanced resilience

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

Potential risks

side-effects on legal system workflows/activities -> covered by regression testing (either unit or functional)

@feiyang3cat feiyang3cat requested review from a team as code owners January 21, 2026 22:24
@feiyang3cat feiyang3cat changed the title wip:Feat/block internal wip: block internal system workflows and activities from getting triggered by users Jan 21, 2026
@feiyang3cat feiyang3cat force-pushed the feat/block-internal branch 4 times, most recently from c1c6b51 to 059ef1b Compare January 21, 2026 23:17
@feiyang3cat feiyang3cat changed the title wip: block internal system workflows and activities from getting triggered by users WIP: block internal system workflows and activities from getting triggered by users Jan 21, 2026
@feiyang3cat feiyang3cat reopened this Jan 22, 2026
@feiyang3cat feiyang3cat force-pushed the feat/block-internal branch 2 times, most recently from 007b616 to 6757de7 Compare January 22, 2026 08:11
@feiyang3cat feiyang3cat changed the title WIP: block internal system workflows and activities from getting triggered by users block internal system workflows and activities from getting triggered by users Jan 22, 2026
@feiyang3cat feiyang3cat force-pushed the feat/block-internal branch 7 times, most recently from 17ee66a to 2ce1e74 Compare January 23, 2026 00:04
} else if !pm.defaultQueueFuture.Ready() {
}
if !pm.defaultQueueFuture.Ready() {
return // not initialized yet
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this line is refined without semantic changing for linter issues

@feiyang3cat feiyang3cat force-pushed the feat/block-internal branch 3 times, most recently from 1ebda01 to 96e0b4f Compare January 23, 2026 03:27
@feiyang3cat
Copy link
Contributor Author

this pr is closed and split into two prs for one workflow and one for activity

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.

1 participant