-
Notifications
You must be signed in to change notification settings - Fork 20
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
Answers + Landings tables no longer refreshing #25
Comments
Hi @nmccormick-bombas did you ever find a resolution to this? I am experiencing the same thing. |
Hey there!
No solution as of yet. One thing that will work - if you setup separate
integrations for your different taboola accounts. A bit of a PIA, but it
will prevent the pipe from breaking. The table only has issues landing when
you have a parent account to multiple taboola accounts.
…On Wed, Oct 14, 2020 at 3:28 PM jackiegillis ***@***.***> wrote:
Hi @nmccormick-bombas <https://github.com/nmccormick-bombas> did you ever
find a resolution to this? I am experiencing the same thing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANJC3UDIZJ7Z6MHWCCE3TWTSKX3UDANCNFSM4P3HGKOA>
.
|
I have noticed the same thing. I managed to get answers when I keep changing tables to replicate settings but now landings won't get updated |
I have the same issue. Managed to fix it back in December by changing the token in typeform and resetting the integration, and making it run the entire integration again. It took hours but seemed to work. This does happen relatively often though so it is confusing that it hasn't been properly fixed. |
I am experiencing the same issue as well. It seems to be a frequent occurrence. Are there any fixes being done right now? |
Having the same problem as well. Issue #28 has some more detail and advice for a workaround. |
Has anyone seen an issue with answers + landings tables being stale? Only my questions table is updating, despite certainty that there have been new responses to the survey I'm pulling in.
The text was updated successfully, but these errors were encountered: