Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Execute API gets called twice when we clone a page #31660

Open
1 task done
sneha122 opened this issue Mar 11, 2024 · 1 comment
Open
1 task done

[Bug]: Execute API gets called twice when we clone a page #31660

sneha122 opened this issue Mar 11, 2024 · 1 comment
Assignees
@rajatagrawal @vsvamsi1
Labels
Bug Something isn't working Integrations Product Issues related to a specific integration Low An issue that is neither critical nor breaks a user flow Medium effort Takes < 2 weeks Needs Triaging Needs attention from maintainers to triage Production Query & JS Pod Issues related to the query & JS Pod Query performance Issues that have to do with lack in performance of query execution

Comments

@sneha122
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Description

If I have a page with 3 table widgets all connected to queries, and If I clone such page, ideally execute call should happen only 3 times, but it's rather happening 6 times, we should not make unnecessary calls to execute API if not required.

Steps To Reproduce

  1. Create a new page
  2. Add 3 table widgets
  3. Add a mock dB query and connect it to all tables
  4. Clone this page
  5. Observe the execute API calls in the network tab
Screenshot 2024-03-11 at 6 05 41 PM

Public Sample App

No response

Environment

Production

Severity

Low (Inconsistent UI/UX)

Issue video log

No response

Version

Cloud/ Self-Hosted - 1.10.0
@sneha122 sneha122 added Bug Something isn't working Performance Pod All things related to Appsmith performance Needs Triaging Needs attention from maintainers to triage labels Mar 11, 2024
@github-actions github-actions bot removed the Performance Pod All things related to Appsmith performance label Mar 11, 2024
@Nikhil-Nandagopal Nikhil-Nandagopal added Production Low An issue that is neither critical nor breaks a user flow labels Mar 11, 2024
@Nikhil-Nandagopal
Copy link
Contributor

Closing this as it does not have an appropriate label associated with a pod

@sneha122 sneha122 reopened this Mar 11, 2024
@sneha122 sneha122 added the Query performance Issues that have to do with lack in performance of query execution label Mar 11, 2024
@github-actions github-actions bot added the Data Platform Pod Issues related to the underlying data platform label Mar 11, 2024
@github-project-automation github-project-automation bot moved this to Needs Triaging in Data Platform Pod Mar 11, 2024
@riteshkew riteshkew added Integrations Product Issues related to a specific integration and removed Data Platform Pod Issues related to the underlying data platform labels Apr 11, 2024
@github-actions github-actions bot added the Query & JS Pod Issues related to the query & JS Pod label Apr 11, 2024
@rohan-arthur rohan-arthur added the Medium effort Takes < 2 weeks label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rajatagrawal rajatagrawal

@vsvamsi1 vsvamsi1

Labels
Bug Something isn't working Integrations Product Issues related to a specific integration Low An issue that is neither critical nor breaks a user flow Medium effort Takes < 2 weeks Needs Triaging Needs attention from maintainers to triage Production Query & JS Pod Issues related to the query & JS Pod Query performance Issues that have to do with lack in performance of query execution
Projects
Data Platform Pod
Status: Needs Triaging
Milestone
No milestone
Development

No branches or pull requests
6 participants
@rajatagrawal @Nikhil-Nandagopal @riteshkew @sneha122 @rohan-arthur @vsvamsi1