Activation Upload Artifact Conflict

[fr4nc1sc0-r4m0n]

Hi folks,

We have been trying to execute some agentic workflows in jobs running sequentially or in parallel in the same workflow and we are facing the same problem when the second activation job runs:

Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Let me put an example:

...
jobs:
  # Step 1: Detect docs drift from recent code changes and create an issue with findings
  audit:
    uses: elastic/ai-github-actions/.github/workflows/gh-aw-docs-patrol.lock.yml@main
    with:
      lookback-window: 1 day ago
      title-prefix: "[autodoc]"
      additional-instructions: |
        Some additional instructions
    secrets: inherit

  fix:
    needs: audit
    if: needs.audit.outputs.created_issue_number != ''
    uses: elastic/ai-github-actions/.github/workflows/gh-aw-create-pr-from-issue.lock.yml@main
    with:
      target-issue-number: ${{ needs.audit.outputs.created_issue_number }}
      draft-prs: true
      additional-instructions: |
        Some additional instructions
...

The problem appears in last step of the activation job added in the compilation process (tested with the last version v0.57.2) which basically adds the actions/upload-artifact step always the same artifact name activation:

- name: Upload activation artifact
        if: success()
        uses: actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f # v7
        with:
          name: activation
          path: |
            /tmp/gh-aw/aw_info.json
            /tmp/gh-aw/aw-prompts/prompt.txt
          retention-days: 1

Making impossible to execute more than one agentic workflow in the same workflow.

Is this something decided in this way by design? Is there any way to bypass this constraint and add some dynamism in the artifact's name?

Thank you in advance!

[pelikhan]

Work happening in #20685