When I have these workflows as **failed
When I have these workflows as failed and when I open them I get this "something went wrong".
When we open the worker logs we don't have nothing there.
14 Replies
Hello there, please share:
- Used twenty version
- Browser console logs
v1.7.6
the browser console logs:
index-B2-4jVOD.js:48 ZodError: [
{
"expected": "string",
"code": "invalid_type",
"path": [
"state",
"stepInfos",
"5adb2605-e499-4e07-898d-0df8cb6c2683",
"error"
],
"message": "Invalid input: expected string, received object"
}
]
We have updated to the v1.10.2
I was reviewing the workflows for the new version and when I try to update the Opportunity Creation workflow I get this error
I had this workflow
The function waas removed when I updated to the new version
When I try to add a new function I get an error:
When I click on the arrow to go back and then I try to edit the same funciton again I get this
@Prastoin I don't know if you're following along or if you need to call someone else, but I'm kinda of lost 😅
Should I start over again and recreate everything from scratch?
Hey @martmull could you please have a look to this when you have some free time please ?
@Pedro Talaia please share you workspace version in database located at
core.workspace.version ( not the ui ) to double you've successfully upgraded to latest version@Baptiste Devessier can you take a look?
ubuntu@ip-X-X-X-X:~$ sudo docker exec -t twenty_db_1 psql -U postgres -d default -c 'SELECT "displayName", "version" FROM core.workspace;'
displayName | version
-------------+---------
A+Casa | 1.10.2
(1 row)
Looks good