Can you check with your browser inspector what happens when submitting the form? You can open the inspector in Google Chrome by right clicking, and selecting Inspect at the bottom. Next, choose the tab Network (it is normally the 4th one)
In my case, I see that the submission was a succes (code 200). You will probably see a code starting with 4 or 5
I am just starting implementing Baserow as a tool for handling a contact database, and I’m not a pro in this area so maybe I’m overcomplicating things.
@Anatole, based on the logs I’ve seen, and the problems that I have identified, I didn’t seem like you’re doing anything out of the ordinary. There is a performance bug in Baserow where if you have many formulas, with many dependencies to other fields, it’s going to do many unnecessary things in the background, which causes your row create / form submissions to timeout. I’m working on a fix as we speak, and I expect to have it solved somewhere tomorrow, Wednesday latest. I’ll keep you posted.
That’s correct. Several performance improvements have been deployed to baserow.io yesterday. The same ones will be included in the release half of December. It will make creating, updating and deleting rows with many field dependencies much faster, and also snapshots and duplications are going to be faster.
hi @bram , does it mean that also the BASEROW_PERIODIC_FIELD_UPDATE_CRONTAB parameter will be improved/optimized in terms of performance, or should I keep it in my Docker container environment even after the December baserow update? I have two formulas with date counting, so I have set the “0 8 * * *” value for them - to eliminate permanent read/write operations.
Thanks!