Hey there! We've found the following might help you get unblocked faster:

• 🧵 SSL Connection error to Postgres DBs

• 🧵 cant connect server to postgres db

• 📚 Viewing Logs

• 🧵 session

If you find the answer from one of these, please let us know by solving the thread!

Hi, could you show exactly the operation that is failing? I wasn't able to reproduce it.

All the fields that now say "null" used to just be empty and that was fine. But if I go in and try to manually manipulate any of these fields I get the original error message that I showed above "invalid input syntax for type timestamp: "null" and if I remove it, it doesn't like that, if I add a timestamp its ok but some of these don't need timestamps. The way my logic is setup its ok for them to be empty until triggered. If that makes sense.

Ah thank you, was able to reproduce! And sorry about that experience, I have a fix in flight and it should be live in a few of minutes!

Ok let me know when you are ready and I'll test it and keep you posted. Thank you!

Paulo sent that message 2 hours ago, so please go ahead and test!

Ok I had been testing with the same result so I thought he might still be working on it. I apologize. When I test now I am getting this.

Hi, are you trying to set a timestamp to empty string? This will not work, if you want to set it to null please set to null like in your screenshot a few comments above.

Not necessarily but they are empty until an event triggers a timestamp to populate. However, that’s not the issue.

The issue is, if I open the record and try to manually manipulate any of the data (which I have been able to do in the past) and then I go to save the record, my changes don’t save and I get the error message that I posted above.

Hi, could you please elaborate on the exact operation failing? Maybe a screenshot/video recording like before, as I'm not able to reproduce.

The null columns are appearing as "null" in the editor right? Where does the empty value come from?

Well, its not doing it anymore. So maybe the fix just took a while or something. Thank you for your support but everything seems to be working like it used to now.

I'm glad it's fixed now, sorry about that experience!

✅ The ticket Database Interface Update Issue has been marked as completed.