microsoft / microsoft/PowerPlatformConnectors

[BUG] Operations are not found, resulting in failures for Power Automate connectors.

Open
#3,552 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Certified Connector

Name of Connector

Cognito Forms

Describe the bug

Users are intermittently seeing one or more of the following errors in Power Automate:

  • Operation not found under connector '/providers/Microsoft. PowerApps/apis/shared_cognitoforms'
  • "Unable to match incoming request to an operation"

This appears to have started with the last release of connector updates.

This issue has been reported in forums before (as early as 2018).
A staff member commented in the forums that this was a known issue (post)
Forum post for incoming request error
Forum post for Microsoft Bookings
Issue in Dynamic 365 repo

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

We are unable to reproduce the issue reliably, but simply trying to use an action with the connector has trigged this bug.

Expected behavior

There should be no error.

Environment summary

Eastern US Power Automate

Additional context

Users are intermittently seeing errors in Power Automate.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Begin by investigating the Cognito Forms connector in the Eastern US Power Automate environment and review the linked forum and Dynamics 365 reports; the work is done when the operation-matching failure is understood, corrected, and verified against the reported errors.

Written by the indexing model from the issue text.

Assessment

Domain
api, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.