I got it! The config field “Created Time Column” seems to be new in “Watch new rows”. Because I have a named column for that, I had to put it in here. Otherwise “_ctime” as the default value does not work. Because I did not check this new config (thought it was there since the beginning), I just ignored it and did not change it. Thus the result was empty, even if there were new rows! Thanks for your help!
@cdb just to explain my trouble. As I changed the old to the new seatable-make.com-module, I also had to change the variables in my follow-up mail-modules in make (the variables out of the seatable). In earlier version, I could just select these variables when including the seateable modules to make.com and establish the connection. Today, I need to run the seatable-watch-new-rows module fist to see the variables from the seatable (column names). But that does only work, when I add new rows in seatable. (so I need a new row, before I can reconfigure the modules) I think that is a change in behavior, at least as I can remember. Do you understand my problem? Now it is solved, but I just wanted to let you know 
Thanks again!
absilutely, the same. every 2-3 days, the depricated error is throws with newly created SeaTable “verified” modules, and we have to recreate not only the modules but also the attributes all over the scenarios costing us 2-3 hours every time. what went wrong with the update on make? can you contact the make support, maybe the issue is on their part - clearly it is not working stable and we no longer can rely on the seatable app and are looking for alternatives sadly
@cdb
Hi Christoph, thanks for your post.
Just to clarify, by “verified” I mean the normal SeaTable modules and not the “rework” modules. When selected, the word “verified” briefly appears.
This is what has happened since MOnday of last week.
16 June: All scenarios stop working, warning of deprecated API. Creating a new SeaTable connection and rooting out “rework” modules and implementing the “verified” modules solves issue.
19 June: Scenarios stop working. Again, deprecated API warning. Change back to original SeaTable connection solves issue.
24 June: Individual ST modules stop working - specifically “List rows”, “Watch new rows”. Reimplementing the modules solves problem.
25 June: Currently no problems.
Theory regarding 24 June issue: The warning I got was that the modules were “deprecated”. In the list of available modules, some modules were list twice, with some bracketed with “deprecated”. It could be that on 16 / 19 June modules that seemed to work again after reestablishing the connection to SeaTable were actually “deprecated” modules. As they seemed to work, I might have not bothered to swap them with newer modules. Perhaps these modules still worked last week, but this week they were taken offline, leaving only the newer modules. When I call up the list of available modules in SeaTable “verified”, I now no longer see any labelled “(deprecated)”.
I hope I am right. @Ivo - this could be your issue.
After the 5.3 update I reworked all my “SeaTable Create a Row”-modules on June 18 with new MAKE connections and new API tokens, and everything has been working smoothly since then.
But now - since yesterday - I’m getting this message:
Please advice me on how to solve it this time.
1 Like
same problem! waiting for advice. reworking all modules again would be a cathastrophy
I am really sorry for all issues that you currently have. Unfortunately my understand it the following:
if you get this error This endpoint is deprecated, than you don’t use the latest version of the SeaTable Make.com App. You have to replace this module.
From my opinion, it is really bad, that Make.com does not provide any information what version of a module you’re using. Also there is no easy way to update a module.
Still it seems that make.com provides a developer tool to update multiple versions at the same time. This is what I found in the community forum of make.com:
- Install the browser Extension “Make DevTools”
- Clone your scenario (for backup)
- Open your Scenario
- Open the Browser Console and switch to Make
- On the left side select Tools
- Use the function Swap App
- Replace SeaTable App with newest Version
The current version of the SeaTable App is v1.36.4.
That’s interesting. Would have saved me some time. The biggest issue I had was the downstream modules (email, OneDrive, etc.) that relied on the references from the upstream SeaTable module. Would the developer tool automatically lead to swapping out those downstream references, or would they need to be altered manually?
Did a quick search and see that Make has a Developer tool for Chrome, that access to the DevTool would be via an extension installed in Chrome?. Is that right? Or is there a a dev tool within the make dashboard somewhere?
Thanks, Christoph, for your suggestion for a solution.
I tried it and ran the swap app feature, but it turned out, that I’m already using version 1.36.4 of the SeaTable App, and therefore I’m still getting the deprecated error.
It is correct, though, that if I manually replace all modules one by one, it seems to be working.
But in my case, it would mean appr. 2 days of work.
I cannot afford this, without beeing sure, that the problem won’t reoccur next week…
Everything was working fine up until yesterday.
You may want to consider switching to n8n …
That is not nor should it be an appropriate solution. I can only assume the issues were like I assume and everything should quiet down.
