AppSpring Docs

write.* diagnostics

Owner: the runtime spec (defs/runtime.ts). The status is the code's own; the exit comes from its category (CATEGORIES). A warning or info code never sets the status or the exit.

Code Category Severity Status Exit Retry Fix Args
write.cascade_forbidden policy error 403 4 no — type, child_type
write.cascade_limit limit error 413 2 no — limit
write.delete_restricted data error 409 6 no — type, child_type, readable_children?
write.dependents_blocked data error 409 6 no — type, child_type, visible?
write.derived_not_writable input error 400 2 no — type, prop
write.forbidden policy error 403 4 no — type, op, prop?, post_image?
write.initial_state_only state error 409 5 no — type, prop, initial
write.invariant_failed data error 409 6 no — invariant, type, message, id?
write.not_found not_found error 404 3 no — type
write.overlap data error 409 6 no — invariant, key
write.prop_unknown reference error 400 2 no yes type, prop, near
write.ref_missing data error 409 6 no — type, prop, target
write.required_missing input error 400 2 no — type, prop
write.stamp_not_writable input error 400 2 no — type, prop
write.state_not_writable input error 400 2 no — type, prop, lifecycle
write.transition_not_from state error 409 5 no — type, transition, from, current?
write.transition_undeclared reference error 400 2 no — lifecycle, transition
write.unique_violation data error 409 6 no — invariant, props
write.value_invalid input error 400 2 no — type, prop, expected
write.version_conflict conflict error 409 6 no — type, expected, actual?

This page as Markdown