Autom Mate Team · Practical example
Start with one specific Service Case when a request behaves unexpectedly. Its context and journey can explain more than a dashboard total.
- Open Service Cases and find the request using its service, time or case identifier. Read Status and Result together.
- Open Context. Confirm the service version, deployment package and environment that actually ran.
- In Journey, choose the affected phase and read Why this result/state? from configured rule to observed work to decision.
- Open the relevant Work Item, then its log history. Compare the actual input, output and error with the outcome you expected.
- Check whether Prove ran and what it verified. Record the first point where actual behavior differs from the request.
Example: Done / Failed means the case completed but its outcome was not achieved. A green execution acknowledgement alone does not explain that result.
For help in this thread, share the version, environment, Status/Result pair and a short redacted error. Leave out tokens, credentials and customer data. That is usually enough to identify the next useful check without posting a complete log dump.
Which phase first differs from what you expected: Govern, Execute or Prove?