Skip to content

"Did not find an interaction that matches the given key" when using provider state #10

"Did not find an interaction that matches the given key" when using provider state

"Did not find an interaction that matches the given key" when using provider state #10

Triggered via issue January 31, 2024 03:25
Status Success
Total duration 32s
Artifacts
call-workflow  /  create-issue-in-pactflow-jira
23s
call-workflow / create-issue-in-pactflow-jira
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
call-workflow / create-issue-in-pactflow-jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
call-workflow / create-issue-in-pactflow-jira
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: atlassian/gajira-login@v3, atlassian/gajira-create@v3, actions/github-script@v6. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.