logic function route triggers are not set during custom application sync

[Patrick-M90]

Bug Description

I have a custom app. Twenty 1.17.0 SDK 0.5.2.
When Syncing my app with yarn app:dev the logicFuntions are created in database but the httpRouteTriggerSettings remain empty.

Thanks for your help

[Patrick-M90]

Here is my analysis:
Bug Report: httpRouteTriggerSettings not populated during syncApplication
Environment: Twenty v1.17.0 (self-hosted, Docker), twenty-sdk v0.5.2

Problem: When syncing a custom app via yarn app:dev, logic function records are created in core."logicFunction", but the JSONB columns httpRouteTriggerSettings and databaseEventTriggerSettings remain NULL. All HTTP routes return 404 TRIGGER_NOT_FOUND.

Root cause: The SDK (v0.5.2) builds the manifest with the property name logicFunctions, but the server-side ApplicationSyncService in v1.17 expects the property name functions. Since manifest.functions is undefined, the sync creates the logic function records but never populates the trigger columns.

Evidence: In twenty-sdk@0.5.2 (dist/cli.mjs, line 1049):

defineLogicFunction: "logicFunctions",
The generated manifest at .twenty/output/manifest.json confirms:

"logicFunctions": [
{
"name": "my-function",
"triggers": [{ "type": "route", "path": "/my-function", "httpMethod": "POST", ... }],
...
}
]
The trigger data is present in the manifest but ignored by the server because it looks for manifest.functions instead of manifest.logicFunctions.

Current workaround: Manually running SQL after every sync to populate the trigger JSONB columns:

UPDATE core."logicFunction"
SET "httpRouteTriggerSettings" = '{"path": "/my-function", "httpMethod": "POST", "isAuthRequired": false}'::jsonb
WHERE name = 'my-function' AND "deletedAt" IS NULL;

[wang2-lat]

This looks like the sync process isn't properly registering the HTTP route triggers for your logic functions. Check if your logic function definitions include the httpRouteTrigger configuration explicitly, and verify that the sync command has permissions to write trigger settings to the database. You might also want to compare your setup against the Twenty SDK 0.5.2 examples to see if there's a schema mismatch.