-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connections: New connections are not being updated in Change connections without a page reload. #6117
Comments
Issue repro in latest canary test pass |
Issue repro in latest canary test pass |
1 similar comment
Issue repro in latest canary test pass |
Issue repro in latest stage test pass |
This bug is in production currently but only affects connections created on custom connectors. I will take a look at it. |
@rllyy97 As this bug is raised in the month of November. Probably could have deployed into production as it does not affect any functionality, but we have to refresh the browser to view the newly created connection. |
@rllyy97 Issue still repro in latest test pass. Probably changes are not have updated into this built. As of now just marking a comment on this bug. |
Issue not repro in updated staging version newcon.working.mp4 |
Describe the Bug with repro steps
a. Cancel order
b. GetMostRecentOrder
c. GetOpenOrders
d. GetOrder
e. submitOrder
Expected: We should see new connections and existing connections (if any) when trying to change the connections.
**Actual:**We can see only existing connections (if any) but not new connections. But we could find the new connection once we reload the browser. It is not updating without reload.
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
reloadconnection.mp4
Browser
Edge
Additional context
Version : 2.41028.1.6
The text was updated successfully, but these errors were encountered: