JSON Parse Error When Scraping

Teable Discussions
,
1

  1. When I scrape with APIFY connector for X/Twitter posts, it shows JSON parse error and restarts the chat contents every few seconds. Sometimes the agent asks me for some confirmation via a dialog but I can see it for a few milliseconds and can not click on that. Also sometimes there are some kind error showing “Minified React error #158” or something (I am not sure about the exact wording.) Please help me solve this issue.

  2. I also see another issue happening from time to time, which is sandbox restarting issue that causes uncommitted codes lost completely and the agent has to code all that again. For that reason, most of my coding session doesn’t go over 1 hour long (or over 1.5 hour long) because of sandbox restarting issue and plan list shows unfinished tasks.

image.png
image.png281×571 12.5 KB

2

Thanks for reporting this. It’s logged as T7651, and we’ll post updates in this topic as it moves along.

3

Hi @HiShahadat,

Thanks for the detailed report. Sorry about the interruptions and lost work.

We’ve noted three issues here:

  1. Apify JSON parsing errors: We’ll check the connector responses and how they’re parsed.
  2. Chat reloading and UI errors: We’re aware of this issue and are focusing on message stream resumption and replay. Our initial suspicion is that reconnecting replays previously received content from the beginning, causing flickering and rendering errors. We’ll also check recent related changes.
  3. Sandbox restarts: We’ve seen memory limits trigger similar restarts before. We’ll check this along with how code is saved and restored. We also support GitHub two-way sync, so you can develop locally and sync changes back to Teable for preview and publishing.

Your report is tracked as T7651, and we’ll post updates in this thread as we have them. Thanks for your patience.

4

Thanks for noting these.

I am not a dev guy. Though I am learning a bit of the dev things to understand better of building my apps. However, I wish the GitHub 2-way sync would work for my existing codebase that developed my other devs back in the days before. I wish I could import the codebase and update the app/website. So it’s not 100% 2-way sync for me. This is kind of a locked in 2-way sync.

Do you have any plans to support this?

5

I have lost data again. That means I lost the time that agent has used to spent for coding. Lost the credits/tokens for that too. Just because of sandbox restart. Can not control myself because of that. Too much frustrating.

6

We’ve started work on T7651. We’ll post here when it’s live.

7

T7651 is live on Teable Cloud. Please check it within 7 days, and reply here if anything is still off.

Self-hosted: pull the latest image to get it.

8

Screenshot_20261011-141846
Screenshot_20261011-1418461080×2400 162 KB

Now it shows “interrupted”. The agent can not finish half of tasks without reoeating “finish the task”.

9

Hi @HiShahadat,

Thanks for the update and screenshot. I’m sorry these interruptions have disrupted your progress and made you repeat some of the work. Here’s where things stand.

Chat fixes are live

We’ve released fixes for:

  • JSON parsing errors in chat.
  • Chat content repeatedly reloading.
  • Confirmation prompts disappearing before you could respond.

These are the improvements covered by the release update above.

Sandbox stability is still being improved

Longer builds can place higher demands on the environment as the app is previewed, compiled, and tested. We’re optimizing resource usage and recovery to make these sessions more reliable.

We’re also looking into the “Interrupted” status you reported and the need to manually continue. Our focus is on reducing interruptions and repeated work during recovery. We’ll share updates here as those improvements are validated.

Bringing an existing project into Teable

I should also clarify my earlier GitHub suggestion: local development is optional. We’re continuing to improve the experience of building directly in Teable, including for people who don’t work with code.

You can already import an existing project’s source code as a ZIP:

Code → … → Import code

A few things to know:

  • Importing replaces the target app’s existing source code.
  • Imported projects need to be compatible with Next.js.
  • GitHub sync currently creates a new repository; connecting an existing repository isn’t supported yet.

If you’d like to give it a try, our code import guide walks you through the steps.

Thanks for taking the time to share these details. Your feedback helps us make Teable more reliable and easier to build with.

10

Hi @Pengap Thanks for the work. The flickering is gone. Yay! :smiley:

However, I see it hangs in the mobile a lot.

Anddd… about the current interruption… it’s very frustrating. I give them some tasks, I assume it would take 5+ hours. But I have to check every few mins if it’s stopped or not (so I can prompt again to “finish the tasks”).

I can not work on other projects without clearing my mind about the Teable chat’s incomplete tasks.

I think a simple task checker would solve it quickly like if there are remaining tasks without any checkmark it will retry itself.

Thanks for the work, again. Awesome.

11

image
image345×686 21.2 KB

This is getting even more frustrating now. It now stops under 10 minutes too. I am thinking that is it happening to me only? Where are other Teable users, do you face this?

12

T7651 is done, so we’re closing this topic. If it comes back, start a new report and link to this one.