Skip to content

Multi-project polling control incorrectly uses first project only #13

Description

@0xroylee

Source workflow reported a bug.

Linear: https://linear.app/roy/issue/ROY-24/should-we-use-sqlite-to-cache-data-or-config-for-scale-up-later
PR: #11

Details:
resolveGlobalPollingSettings returns projects[0].polling (src/workflow.ts:88-100), and shouldStopPolling uses that single config for global stop decisions (src/workflow.ts:102-117). In --all-projects mode, per-project polling settings (interval/maxCycles/exitWhenIdle) are ignored for projects beyond the first, which can stop polling too early or keep polling unexpectedly when project configs differ.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions