Notification workflow status

SunrAI does not currently provide an active managed-notification workflow builder or executor.

What you can configure

Notification preferences control how you receive each supported, code-owned event in the current team. The available channels are in-app, email, and browser push when that channel is configured.

Every visible row has a direct product trigger, an authorized recipient rule, a destination, and independently tracked channel outcomes. Changing a personal preference does not create a team automation.

Historical workflow records

Older SunrAI schema includes workflow, step, version, and scheduled-notification records. Those records are retained as history only:

• No dashboard builder or activation control is available.
• The workflow dispatcher schedules nothing.
• The historical fire and claim-sweeper endpoints are unscheduled compatibility surfaces and return HTTP 410 after authentication.
• Support cannot activate those rows as a managed workflow.

SunrAI keeps the historical schema because an empty table or an old row is not permission to delete customer or audit data. A future workflow product would need a separately reviewed design and would replace a direct producer end to end; it would not run beside one and duplicate delivery.

Troubleshooting

"I changed my preferences but no automation was created." — This is expected. Preferences only apply to supported direct notification events.

"I need a new event or recipient rule." — Contact support@sunrai.ai with the business event, intended recipients, destination, and desired channels. The request must be implemented and tested as a product contract before it can appear as a preference.

"An old workflow record still exists." — Historical records are retained but cannot execute through the retired workflow boundary.