Skip to content

PLEX-2557: adjusting log levels depending on the type of capability error#22268

Open
fernandezlautaro wants to merge 1 commit intodevelopfrom
PLEX-2557
Open

PLEX-2557: adjusting log levels depending on the type of capability error#22268
fernandezlautaro wants to merge 1 commit intodevelopfrom
PLEX-2557

Conversation

@fernandezlautaro
Copy link
Copy Markdown
Contributor

@fernandezlautaro fernandezlautaro marked this pull request as ready for review April 30, 2026 12:55
@fernandezlautaro fernandezlautaro requested review from a team as code owners April 30, 2026 12:55
Copilot AI review requested due to automatic review settings April 30, 2026 12:55
@github-actions
Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 30, 2026

✅ No conflicts with other open PRs targeting develop

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Risk Rating: LOW

Adjusts logging verbosity so capability user errors are less noisy while system/unknown errors are more visible, improving operational signal for workflow/capability failures.

Changes:

  • Promote capability execution failures that are system/unknown-origin from Debugw to Errorw in the workflow capability executor.
  • Demote trigger registration failures that are user-origin (non-retriable) from Errorw to Debugw in the remote trigger publisher.

Scrupulous human review suggested (small but operationally relevant):

  • core/services/workflows/v2/capability_executor.go around the capability error classification/logging path (log volume/alerting impact).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
core/services/workflows/v2/capability_executor.go Raises log level for system/unknown capability execution failures to improve visibility.
core/capabilities/remote/trigger_publisher.go Lowers log level for user-origin registration failures to reduce noise while preserving retry behavior for system errors.

Comment thread core/services/workflows/v2/capability_executor.go
@trunk-io
Copy link
Copy Markdown

trunk-io Bot commented Apr 30, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
Test_CCIP_TokenTransfer_LnR_EVM2Aptos The test failed because the Aptos node API could not be exposed on port 8080, causing the container to not be accessible as expected. Logs ↗︎
Test_CCIP_TokenTransfer_LnR_without_TransferRef_EVM2Aptos The test failed because the Aptos node API could not be accessed on port 8080, preventing the test from proceeding. Logs ↗︎

View Full Report ↗︎Docs

@cl-sonarqube-production
Copy link
Copy Markdown

@ilija42 ilija42 enabled auto-merge May 4, 2026 15:20
@ilija42 ilija42 added this pull request to the merge queue May 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 4, 2026
@ilija42 ilija42 added this pull request to the merge queue May 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 4, 2026
@DylanTinianov DylanTinianov added this pull request to the merge queue May 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 4, 2026
@DylanTinianov DylanTinianov added this pull request to the merge queue May 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 4, 2026
@DylanTinianov DylanTinianov added this pull request to the merge queue May 5, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 5, 2026
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.

6 participants