Using the Activity Stream to review a Flow Designer injection request

Problem

The integration I configured using Flow Designer isn't working. Where do I find logs to troubleshoot, and what can I do if I don't see any Activity entries?

Environment

All versions of xMatters

Resolution

You can use the Flow Activity section to monitor your integration's requests in the system and view the details and history of completed requests.

1. Open the Activity Panel from within Flow Designer on the upper right.
   

2. Along the bottom panel, make sure logging is enabled.
   

3. Click the link for one of the integrations to see the log it has generated.
   

Troubleshooting when you don't see Activity entries

If you're not seeing any logs in the Activity stream:

• Make sure that logging is enabled for your integration.

• Check for any duplicate workflows where the request may be directed.

• Confirm that your test or incoming requests are being sent to the correct, enabled Flow Designer endpoint and that authentication is configured correctly.

• Review the Reports > Signals report in the xMatters web UI to see whether requests reached Flow Designer or failed earlier in the pipeline. If the Signals report shows failures before Flow Designer (for example, authentication issues or a disabled/non-existent endpoint), no Activity log entries will be created.

• Check that you're looking within the Activity log retention window. Activity entries are only kept for a limited time (typically 7–30 days), so older executions may no longer appear in the Activity tab.

Logs should look similar to the following if logging was enabled:

Log Size Limitations

xMatters Flow Designer has a 3MB log size limit to protect system performance. When logs exceed this size, they are truncated, which can make debugging difficult.

To manage log sizes effectively:

• Use more specific logging by only capturing critical information (like subscription IDs and update reasons) instead of full data sets.

• Consider disabling logging of HTTPS response data on a request-by-request basis. This allows the response to be returned to the script but not appear in the Activity log.

• For steps requiring extensive logging, consider running the step on an xAgent, which does not have the same log file size restrictions as the hosted system.