microsoft / microsoft/PowerPlatformConnectors

[BUG] When Updating Connector the changes take 1 day to reflect and sometime don't

Open
#3,947 4 comments 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

SGEV

Describe the bug

I'm at my minister and we user Custom Connector for an app called SGEV. When we update the connector, the changes made in it only reflect the next day or don't, so we have to recreate one always, that's really frustrating. We check on the Internet and we see that others don't seem to have to same bug, because they can delete the connector and readd it, but for us it doesn't work. We talked to a Microsoft guy but he did not find anything having try all possible things.
So we ask ourself if it is our Network that is in problem? Or the cache doesn't refresh? Let me know, but I think there is an issue here.

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

In our organisation, just make a change in our connector outside the Security section, and then the connector won't update.

Expected behavior

The connector update immediately or we are able to have workaround to see the changes made.

Environment summary

Gourvernment minister in Quebec City

Additional context

We are with Azure

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 code entry points are mentioned. Start by reproducing the SGEV custom connector update in Azure and compare updates inside and outside the Security section; done means identifying why changes are delayed or missing and documenting a reliable fix or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.