Known Limitations

Known platform constraints

This page lists technical and operational constraints already identified in ENSPACE that may impact specific usage scenarios. These limitations are monitored by the technical team and updated as new constraints are identified or resolved.

Emails

The recipient field ("To") of emails sent by the platform does not accept addresses containing the "&" character. Sending to these addresses may fail silently. If necessary, use an alternative email address for the recipient.

If you identify unexpected behavior or issues not listed here, please contact ENSPACE support for evaluation.

Task descriptions do not render tables

Tables placed in a task description (including those generated by a Task node in Spaceflow) are not displayed as a table in the task panel: the content collapses into a single paragraph with no line separation. To list information in a description, use one paragraph per line. In emails the behaviour is the opposite — there, a table is the only formatting that survives.

Dynamic task due dates display one day early

When a task due date is calculated from a date field (for example, "5 days before the due date"), the calculation runs in UTC over a date with no timezone. In negative offsets such as Brasília, the screen shows the previous day at 21:00. When setting the offset, allow one extra day so the deadline appears on the intended date.

A category that has ever had items cannot be deleted

Deleting a category is refused while items are associated with it — and the count includes items that were already deleted. In practice, a category created for testing that once received any item stays in the workspace.

Deleting an item does not delete its tasks

When an item is deleted, tasks that pointed to it remain open in the task list with no associated item. They must be deleted separately.

Dates written by a flow are not normalized

A date field filled in by a flow stores exactly the text it receives. If the expression builds 2026-8-7 instead of 2026-08-07, that is what gets saved — and period filters then compare text, returning wrong results. Always build dates as YYYY-MM-DD, with leading zeros.

Formatting an empty field prints the format spec

The formatting function applied to a field with no value prints its own formatting configuration in place of the value. Only format fields that are filled in at the moment the text is assembled.

Spaceflow description limited to 255 characters

Descriptions longer than 255 characters cause the flow save to fail with no specific message.

Sent Emails list shows the recipient in the copy column

Under Settings → Emails → Sent Emails, the recipient address appears in the "Email in Copy" column while the "Email" column is empty. This affects the list display only: delivery to the configured recipient works normally.

A required field with no source blocks task completion

If a required field on a task form stops being filled in — for example because the field that fed it was removed from the creation form — the task will not complete: the button responds, nothing happens, and no message is shown. When removing a field from a creation form, check whether any task form depends on it.

A form only opens in tasks of the same category

A form belongs to a category. A task created by a flow can only open forms belonging to the category of the item it updates. A form from one category cannot be used in a task that updates an item of another.

Read-only fields are not saved by the form

A field marked as read-only on a form is displayed but not submitted on save. On update forms this is the expected behaviour: the value already stored on the item stays intact. On creation forms, however, a read-only field with a pre-filled value will not be stored — use the disabled field option instead, which keeps the value in the submission.

Expression calculations compare numbers only

The calculation function in expressions accepts numeric comparisons (for example, a value greater than a threshold) and can return text as the result. Text-to-text comparisons are not supported: the flow step does not run and no record is created, with no error message. To show or hide information based on whether a text field is filled in, use flow routes or make the field required at the source.

Conditional blocks in email bodies only work in Email Templates

The {{#if-condition ...}} conditional block is interpreted in Email Templates, but not in the Spaceflow email node. In the node the markers disappear from the text and the content between them is always displayed, even when the condition is false — with no error message. For an email with conditional sections, use an Email Template; inside a flow, split the paths with routes and one email node per path.