You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, @elrondwong! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing.
The error you're encountering, "null value in column 'updated_at' of relation 'workflows' violates not-null constraint," is due to the updated_at field not being set when creating a new workflow. This field is expected to have a value, and the application logic should ensure it is set.
To resolve this issue, ensure that the updated_at field is assigned a value when creating or updating a workflow. In the Dify application, this is typically done by setting the updated_at field to the current UTC time using datetime.now(timezone.utc).replace(tzinfo=None) in the sync_draft_workflow method [1][2].
Check your application code to ensure that this logic is correctly implemented and that the updated_at field is being set appropriately during the workflow creation process.
Self Checks
Dify version
0.10.2
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
run server
create a workflow from blank
flash console log
✔️ Expected Behavior
Create workflow from blank successfully
❌ Actual Behavior
UI hangging
api logging erros
The text was updated successfully, but these errors were encountered: