Question 1

What should I review when a workflow is flagged?

Accepted Answer

Sign in and open Dashboard, then select the failed workflow. Review its latest failure reason and available evidence, then inspect the run history to understand the recorded outcomes. Workflow pages require an authenticated session; if you are signed out, the dashboard sends you to /login.

Question 2

What can I do today?

Accepted Answer

For a failed latest run, the incident panel lets you acknowledge the failure or mark the incident resolved. Its timeline displays when those actions were recorded, with each timestamp associated with a run. Marking an incident resolved records a tracking decision; it does not repair the workflow or verify that it is healthy.

Question 3

How are supported fixes approved?

Accepted Answer

For the current failed run, an admin can request an enabled Retry or Restart action. When its policy requires approval, the request is saved as pending until an admin approves or rejects it. Rejection is recorded without dispatching the action. Approval is recorded and sent through the supported-action path, but no remediation executor is connected yet, so the action is recorded as not dispatched rather than reported as successful.

Question 4

How do pre-approved policies fit?

Accepted Answer

Admins can configure Retry and Restart separately for each workflow. Both actions default to disabled and approval required. Disabled actions cannot be requested; enabled actions that require approval create a pending review request. The app has no connected remediation executor yet, so an enabled action without approval is not dispatched.

Question 5

Will every issue be fixed automatically?

Accepted Answer

No. A supported fix may not be offered, an issue may fall outside an applicable future policy, or a person may need to investigate and handle it. Tanglewake does not promise automatic resolution for every workflow issue.

Question 6

What is recorded?

Accepted Answer

The incident timeline records acknowledgement and resolution actions and their timestamps, each associated with a run; it does not identify the acting user. Separately, remediation request history records approval or rejection, reviewer, review time, and the dispatch outcome when an action was approved. These request decisions do not mean the workflow was repaired.