SlackOperator → Raha → Nima
Continue manually from the brief. Nima fixes the folder scope and tests the same case; full Drive access is not the fix.
ScaleOperate03 / 04
The team uses the workflow daily.
Who keeps it working?
Product facts may become stale, Drive access may fail or model output may weaken. Users need a support contact and technical owners need failure and cost visibility. Define ownership, monitoring, manual fallback and how a changed version is reviewed.
Workflow operations cardWho supports it, what triggers an alert, how work continues and how changes are accepted.
ActivepiecesWhen work stalls / workflow supportILLUSTRATIVE
Google DriveEXAMPLE SITUATIONThe folder connection returns 403.
Slack
LangfuseEXAMPLE SITUATIONA new output misses the brand tone.
SlackLeila + Nima
Inspect the trace, add the case to the Dataset, revise with brand examples and compare scores. Do not release before review.
Claude CodeEXAMPLE SITUATIONThe builder proposes a new model.
SlackNima → Leila → Sara
Run current and proposed versions on the same Dataset. Compare quality, behavior and cost; the work owner then decides whether to replace it.
FIELD, its figures, conversations and decisions are fictional worked examples.
Compare outputs before changing the model or tool.
The builder reruns the same tests and scoring criteria on the new version. The reviewer compares old and new outputs. A version with weaker quality or changed authority does not automatically replace the current one.
LangfuseCompare versions / before a model or prompt changeILLUSTRATIVEClaude CodeNima has a proposed revision to improve tone. Run the same campaign Dataset on both versions, then Leila compares the outputs.
v0.3
Brand score: 3.6/5
Email copy was generic and needed concrete brand examples.
v0.4
Prompt revised with brand examples; results not measured yet.
Compare the same inputs, claims, approval, duplicate handling, tone and cost.
FIELD, its figures, conversations and decisions are fictional worked examples.
Workflow operations card
Review incidents, quality, cost and adoption regularly. Use these records when deciding whether to continue or expand.
NotionOperating runbook / CampaignILLUSTRATIVEIf I am away, does the team know what to do?
Technical owner: NimaWork owner: Sara
When a run stalls
Send the campaign ID and failing step to Raha in #ai-campaigns. Nima inspects the Activepieces run and Langfuse trace. Keep the flow stopped if sources or permissions fail; the team continues manually from the brief.
Regular review
- Leila reviews weak outputs and brand examples.
- Nima reviews connection failures, model costs and tests.
- Sara and Raha review delivery time, actual use and team barriers.
Before replacing a version
Test the proposed version on the same cases. The quality reviewer and work owner review the comparison. Retain the previous version and manual path until the new one is accepted.
FIELD, its figures, conversations and decisions are fictional worked examples.