Error Handling & Reliability
Improved error messaging and validation
We’ve enhanced error handling across key areas of the platform to provide clearer guidance, reduce debugging time, and help users resolve issues faster.
Clearer permissions feedback when creating sequences
We’ve improved the error messaging shown when a Config Admin user attempts to create a sequence without sufficient permissions.
Users who are not owners of any Object Class will now see a clearer, more informative message explaining why the action cannot be completed, helping to remove ambiguity and guide next steps.
New message:
You can only create sequences for classes you own. Currently you are not an owner
of any class. Hence will not be able to create this sequence.
Click 'Cancel' to leave this page.Improved validation when configuring the Loop actor
We’ve introduced enhanced validation for the Loop actor to help catch configuration issues earlier in the process.
What’s improved: The JSON Path field is now validated in real time to ensure it resolves to a valid iterable array, preventing errors from surfacing later during execution.
| clipboard-202511261230-yexmo.png | clipboard-202511261207-5z011.png |
If the JSON Path does not point to an array, the field will be highlighted in red and the actor cannot be saved until the issue is resolved.
| A warning icon will also appear on the Sequence canvas, making it easy to identify misconfigured actors at a glance | clipboard-202511261221-myfll (1).png |
These improvements help reduce time spent debugging and provide greater confidence when building complex workflows.
Note: This validation does not apply to Loop actors configured after a Document Picker actor.
Enhanced error reporting for Object Class relations
We’ve introduced more detailed validation and error reporting when removing Object Class relations via:
PATCH /api/object-models/<id>/What’s improved: The API now returns clearer 400 Bad Request responses, explicitly identifying which Sequences, Document Templates, or Records are preventing the operation, along with relevant IDs where applicable.
This makes it significantly easier to understand dependencies and take the necessary steps to resolve them, streamlining both development and maintenance workflows.