Skip to content

External feed trigger executions can result in large log volumes #10015

@bec-callow-oct

Description

@bec-callow-oct

Severity

No response

Version

Earliest tested was 2025.4.10664

Latest Version

I could reproduce the problem in the latest build

What happened?

When a package is required by an external trigger, Octopus retrieves its latest version information from the feed and writes a log for each trigger, even for triggers that do not require the package. When there are many active triggers and many packages, this can result in a large volume of logs.

Reproduction

  1. Create Project1 and Project2
  2. Create an external feed with two packages
  3. In Project1, create a run a script step with referenced package A and set up an external feed trigger to create a release when package A version changes
  4. In Project2, create a run a script step with referenced package B and set up an external feed trigger to create a release when package B version changes
  5. In the external feed, increment the version of Package A only
  6. View the task log to see that both version information retrieval is logged for both package A and package B for both external triggers

Error and Stacktrace

More Information

No response

Workaround

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugThis issue represents a verified problem we are committed to solving

    Type

    No type
    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