Chatwoot 4.0.2 is a beta release candidate

[andreasdueren]

@girish any idea what is causing this?

[girish]

@andreasdueren said in Chatwoot 4.0.2 is a beta release candidate:

Mar 15 11:48:22 E, [2025-03-15T10:48:22.644055 #26] ERROR -- : [ActiveJob] [Inboxes::FetchImapEmailsJob] [b146536f-4a34-4634-b535-43dfd0279a53] PG::NotNullViolation: ERROR: null value in column "display_id" of relation "conversations" violates not-null constraint

This seems like some error in the app.

[girish]

@andreasdueren did you try deleting/updating/resaving the inbox configuration ? It looks like something is null when it shouldn't be.

[andreasdueren]

@girish Yes I updated/resaved the inbox configuration various times. I don't really want to delete the whole inbox because then I would loose all my custom data like private comments and outwards communication. I'll try to add another one and see if that works.

[andreasdueren]

@andreasdueren said in Chatwoot 4.0.2 is a beta release candidate:

I'll try to add another one and see if that works.

Didn't seem to work either

[andreasdueren]

I believe I solved this.

1. My system was creating contacts for incoming emails
2. When trying to create conversations, it failed with: null value in column "display_id" violates not-null constraint
3. This caused all emails to be dropped

How I fixed it:

1. I checked for the sequence in PostgreSQL:

   SELECT last_value FROM conversations_display_id_seq;
   

   Got error: relation "conversations_display_id_seq" does not exist

2. I checked available sequences and found only:

   • conversation_participants_id_seq
   • conversations_id_seq

3. I created the missing sequence:

   CREATE SEQUENCE conversations_display_id_seq;
   

4. I linked it to the conversations table:

   ALTER TABLE conversations ALTER COLUMN display_id SET DEFAULT nextval('conversations_display_id_seq');
   

5. I initialized it with current data:

   SELECT setval('conversations_display_id_seq', (SELECT COALESCE(MAX(display_id), 1) FROM conversations), false);
   

6. Then I restarted my Chatwoot app to apply these changes.

7. Seems to all work now.

[fbartels]

@andreasdueren thanks for the step by step. I did not have time to really dive into this from my side, but this seems to have done the trick.

[joseph]

@andreasdueren great write up. I am curious how you came to find such database details? Did you guess your way or is there some upstream issue to track?

[andreasdueren]

@Joseph Asked Claude to help me troubleshoot lol. Apparently this is a common PostgreSQL sequence issues in Rails applications.

[joseph]

@andreasdueren oh good idea. I have been using mistral so far. should check out claude