Skip to content

Operations can't access errors from previous operations anymore #26207

@Dominic-Marcelino

Description

@Dominic-Marcelino

Describe the Bug

Previously operations could access throws Errors from previous operations.

Script Operation example

const errorMessage = data.$last.message

Send notification example

// Message

Full-error:
{{ operation_key }}

Both doesn't works anymore. I assume it's due to the sieveFunctions function implemented in #25106

To Reproduce

  1. Create an operation, which throws an error
  2. Add a script-operation to the error-path
  3. Check $data.last --> it's an empty object
  4. Try to include the error in an notification: --> empty object too

Directus Version

v11.9.3

Hosting Strategy

Self-Hosted (Docker Image)

Database

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions