Possibility to set custom data freshness rate for connector [161156075]

Feature Request

Status Update

No update yet.

Description

ma...@rampfy.com

created issue #1

Jul 14, 2020 04:48PM

We built a community connector that gets informations from our software.
But the default 12 hours it's too long. Some of our informations need to be refreshed in Data Studio in a shorter period of time.

Comments

ma...@zestia.com <ma...@zestia.com> #2Mar 3, 2021 11:35AM

Hello,

Thank you for contacting the Google Cloud support team.

I have gone through your reported issue, however it seems like this is an issue observed specifically at your end within your project environment. It would need more specific debugging and analysis. To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking here. Our support team will prioritize your request and provide you with the assistance you need.

Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system. I'm going to close this issue which will no longer be monitored. If you have any additional issues or concerns, please don’t hesitate to create a new issue on the Issue Tracker.

Thank you, we appreciate your cooperation!

[Deleted User] <[Deleted User]> #3Aug 2, 2021 03:37PM

I'd like to see the data freshness of a community connector configured via the appsscript.json manifest file.

cy...@gmail.com <cy...@gmail.com> #4Aug 2, 2021 06:15PM

upvote as PR

yo...@dooblo.com <yo...@dooblo.com> #5Jun 14, 2022 03:11PM

Upvote.
Definitely need a way to configure anything else than 12 hours for live or semi-live data

[Deleted User] <[Deleted User]> #6Jul 22, 2022 01:58PM

Upvote. Need this as well.

tr...@gmail.com <tr...@gmail.com> #7Oct 31, 2022 09:51AM

Upvote. I want to use biological data .
It’s important to get fresh data.

vl...@playtini.ua <vl...@playtini.ua> #8Jan 14, 2023 04:27PM

ra...@thrio.com <ra...@thrio.com> #9Feb 2, 2023 10:20AM

sa...@gnucoop.com <sa...@gnucoop.com> #10Mar 2, 2023 11:31AM

fi...@gmail.com <fi...@gmail.com> #11Jun 10, 2023 02:12PM

ds...@gmail.com <ds...@gmail.com> #12Jun 28, 2023 09:35AM

This is a real limiter and issue for some use cases, would support this feature being added.

mi...@gmail.com <mi...@gmail.com> #13Aug 30, 2023 05:24PM

m....@gmail.com <m....@gmail.com> #14Sep 2, 2023 11:46PM

Please make this feature

ar...@writerrelocations.com <ar...@writerrelocations.com> #15Oct 9, 2023 07:15PM

Kindly add this as a feature

br...@gmail.com <br...@gmail.com> #16Nov 7, 2023 03:39AM

such a crazy long time. up

gu...@gmail.com <gu...@gmail.com> #17Nov 9, 2023 01:58PM

le...@asksuite.com <le...@asksuite.com> #18Nov 27, 2023 12:25PM

j....@dailyfoods.cl <j....@dailyfoods.cl> #19Jan 31, 2024 05:01PM

lu...@snowflake.com <lu...@snowflake.com> #20Apr 12, 2024 08:42AM

Yep, we need this feature.

ri...@nielsen.com <ri...@nielsen.com> #21Apr 15, 2024 09:15PM

Add me to the list. 12 hours is too long in my case.

pe...@matrixrunner.net <pe...@matrixrunner.net> #22Apr 15, 2024 09:18PM

Please add this feature, the same options as a google sheet would be good.

in...@techfinna.com <in...@techfinna.com> #23Apr 16, 2024 09:18AM

I see it's been 4 years since this request was posted and there is no update or workaround from Looker.
UPVOTE

vl...@playtini.ua <vl...@playtini.ua> #24Apr 22, 2024 07:06PM

12 hours is too much

an...@gmail.com <an...@gmail.com> #25May 30, 2024 07:21PM

upvote, 12 hours is way too long

da...@google.com <da...@google.com> #26Sep 13, 2024 04:14AM

upvote, 12 hours is way too long

yn...@uc.cl <yn...@uc.cl> #27Oct 31, 2024 04:29AM

upvote, 12 hours is way too long

to...@abndigital.com.ar <to...@abndigital.com.ar> #28Oct 31, 2024 01:35PM

upvote. need to provide our users flexibility here

hk...@thinkmarkets.com <hk...@thinkmarkets.com> #29Nov 11, 2024 07:49AM

upvote, 12 hours is way too long

Issue 161156075

Description

Issue summary

Comments

ma...@zestia.com <ma...@zestia.com> #2Mar 3, 2021 11:35AM

[Deleted User] <[Deleted User]> #3Aug 2, 2021 03:37PM

cy...@gmail.com <cy...@gmail.com> #4Aug 2, 2021 06:15PM

yo...@dooblo.com <yo...@dooblo.com> #5Jun 14, 2022 03:11PM

[Deleted User] <[Deleted User]> #6Jul 22, 2022 01:58PM

tr...@gmail.com <tr...@gmail.com> #7Oct 31, 2022 09:51AM

vl...@playtini.ua <vl...@playtini.ua> #8Jan 14, 2023 04:27PM

ra...@thrio.com <ra...@thrio.com> #9Feb 2, 2023 10:20AM

sa...@gnucoop.com <sa...@gnucoop.com> #10Mar 2, 2023 11:31AM

fi...@gmail.com <fi...@gmail.com> #11Jun 10, 2023 02:12PM

ds...@gmail.com <ds...@gmail.com> #12Jun 28, 2023 09:35AM

mi...@gmail.com <mi...@gmail.com> #13Aug 30, 2023 05:24PM

m....@gmail.com <m....@gmail.com> #14Sep 2, 2023 11:46PM

ar...@writerrelocations.com <ar...@writerrelocations.com> #15Oct 9, 2023 07:15PM

br...@gmail.com <br...@gmail.com> #16Nov 7, 2023 03:39AM

gu...@gmail.com <gu...@gmail.com> #17Nov 9, 2023 01:58PM

le...@asksuite.com <le...@asksuite.com> #18Nov 27, 2023 12:25PM

j....@dailyfoods.cl <j....@dailyfoods.cl> #19Jan 31, 2024 05:01PM

lu...@snowflake.com <lu...@snowflake.com> #20Apr 12, 2024 08:42AM

ri...@nielsen.com <ri...@nielsen.com> #21Apr 15, 2024 09:15PM

pe...@matrixrunner.net <pe...@matrixrunner.net> #22Apr 15, 2024 09:18PM

in...@techfinna.com <in...@techfinna.com> #23Apr 16, 2024 09:18AM

vl...@playtini.ua <vl...@playtini.ua> #24Apr 22, 2024 07:06PM

an...@gmail.com <an...@gmail.com> #25May 30, 2024 07:21PM

da...@google.com <da...@google.com> #26Sep 13, 2024 04:14AM

yn...@uc.cl <yn...@uc.cl> #27Oct 31, 2024 04:29AM

to...@abndigital.com.ar <to...@abndigital.com.ar> #28Oct 31, 2024 01:35PM

hk...@thinkmarkets.com <hk...@thinkmarkets.com> #29Nov 11, 2024 07:49AM

Add comment

Issue metadata