le-app/directus/flows.md

Directus flows

Two active event-triggered flows were exported. Both run with accountability all. The export deliberately replaces every operation's options with only options_keys; code, filters, collections, queries, keys, error messages, status codes, and event scopes are not available. The graphs below are therefore structural, not behavioral proofs.

unique_key_claims

Description: “A flow for setting a unique key for each claim to prevent duplicates.”

Run Script (exec_5dli5)
  resolve -> Read Data (item_read_e4myo)
               resolve -> Condition (condition_s458i)
                            resolve -> Throw Error (throw_error_22tpm)
                            reject  -> end
               reject  -> end
  reject  -> end

• Trigger: event.
• Flow option keys: type, scope, collections, return.
• Script option key: code.
• Read option keys: permissions, emitEvents, collection, query.
• Condition option key: filter.
• Error option keys: status, message, code.

Unresolved: the triggering collection/event, how the unique key is calculated, what data is queried, the condition's polarity, error response, and whether the graph handles races atomically. The description suggests duplicate prevention, but omitted options prevent verification.

claim_auto_assign

Description: “Assigns a claimant to owner and rejects other pending claims.”

Condition (condition_dl7cj)
  resolve -> Read Data (item_read_oyges) -> end
  reject  -> end

• Trigger: event.
• Flow option keys: type, scope, collections.
• Condition option key: filter.
• Read option keys: permissions, emitEvents, collection, key.

Unresolved: the triggering collection/event, condition, item key, read collection, and any mutation that performs the assignment or rejection. The exported graph contains only a condition followed by an item-read operation; no update operation is visible. The description's assignment behavior therefore cannot be reconciled with the sanitized graph without the omitted options or additional extension/hook behavior.

Refreshing flow documentation

A future sanitized export should retain non-sensitive structural option values such as event type, collection name, and graph routing when safe, while continuing to remove credentials, destination addresses, headers, code containing secrets, and personal data. Each retained value must be reviewed rather than copied wholesale.