Skip to content

[Bug] [Module Name] Bug title V3.3.2 dependent component Check interval invalidate #18692

Description

@HiR0y

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Image Image

as picture, check interval set 900s ,but still interval 10s in log.

What you expected to happen

check interval set 900s , actual interval 900s in log.

How to reproduce

use dependent component , set check interval >10s ,no special scenario

Anything else

No response

Version

3.3.2

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. Mrhs121 commented on Oct 10, 2026

    @Mrhs121
    Contributor

    @ruanwenjun please assign to me

  2. Mrhs121 commented on Oct 10, 2026

    @Mrhs121
    Contributor

    the task executor refactoring in #16790 removed getAsyncTaskStateCheckInterval(), which previously read the configured checkInterval. The replacement execution path uses a hardcoded DEFAULT_TRACK_INTERVAL = 10_000 milliseconds in AbstractTaskExecutor.

    As a result, dependent tasks are checked approximately every 10 seconds, regardless of the configured interval, including 900 seconds.

  3. added this to the 3.5.0 milestone on Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions