on.workflow_call event does not support on.reactions

[v1v]

We use workflow_call to customise the agentic workflows using github reusable workflows.

It worked fine in version: v0.68.3

But it stopped working in the newer version: v0.79.3

elastic/ai-github-actions@726134d#diff-b419a21af82501031de11cb83b23f240b10b6b6129a007115610d104f3d7cfdcL146

Do you know how can I get back to the former approach? or what's the upgrade path?

[pelikhan]

@v1v please run the debug.md agent to produce a detailed error report on the issue.

[v1v]

I'll analyze this workflow run to help debug the issue.The workflow "Mention in Issue" is failing with a 403 Forbidden error when trying to add a reaction to an issue comment. Let me check the workflow file to see how it's configured:## Workflow Failure Analysis

The workflow "Mention in Issue" failed with a 403 Forbidden error when trying to add a reaction to an issue comment.

Root Cause

The error occurred at this step:

POST /repos/elastic/****/issues/comments/4706220230/reactions - 403
Error: Resource not accessible by integration

The workflow is attempting to add an emoji reaction (👀 "eyes") to an issue comment but lacks the necessary permissions. This is a permissions mismatch issue.

The Problem

Looking at the workflow file, the permissions are defined at the top level:

permissions:
  actions: read
  contents: write
  discussions: write
  issues: write
  pull-requests: write

However, the issues: write permission doesn't include the ability to add reactions. In GitHub Actions, reactions require explicit permissions that are separate from issue write permissions.

Solution

Add the reactions permission scope to the workflow. Update the permissions block:

permissions:
  actions: read
  contents: write
  discussions: write
  issues: write
  pull-requests: write
  reactions: write  # Add this line

Note: The reactions permission scope may not be a standard top-level permission. The actual fix depends on the reusable workflow being called (elastic/ai-github-actions/.github/workflows/gh-aw-mention-in-issue.lock.yml@v0).

Alternative Solutions

1. If the token is the issue: The workflow uses COPILOT_GITHUB_TOKEN secret. Verify that this token has permissions to add reactions. You may need to use ${{ secrets.GITHUB_TOKEN }} instead or update the token's permissions.

2. Check the reusable workflow: The actual action that adds reactions is in the reusable workflow at elastic/ai-github-actions. You may need to update that workflow or ensure it properly inherits permissions.

3. Remove the reaction step: If adding reactions isn't critical, modify the reusable workflow to skip this step or handle the 403 gracefully.

References

• GitHub Docs: Create reaction for an issue comment
• Workflow run logs