For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • What To Monitor
  • Common Failure Causes
  • What To Do When Something Fails
  • API reference
Workflows

Monitoring and Audit

Was this page helpful?
Previous

Common Use Cases

Next
Built with

Workflows are under active development and not yet generally released. The UI and API may change without notice. If you want early access, contact Solvimon support.

Once a workflow is active, you need to be able to answer two operational questions:

  • Did it run?
  • Did the customer get the intended outcome (for example an email)?

What To Monitor

  • Execution success rate: actions should consistently succeed.
  • Deliverability: in your email provider, confirm sends are accepted and not bouncing.
  • Cadence: for overdue reminders, confirm your schedule matches expectations.

Common Failure Causes

  • Email integration is not active or not fully configured (domain not verified).
  • Template name mismatch between Solvimon and the email provider.
  • Locale-specific template enabled but missing for a customer locale.
  • Pay link requested but payment collections are not configured.

What To Do When Something Fails

  • Check the workflow status and scope.
  • Confirm the trigger exists for the invoice/payment.
  • Check the execution record for the action result and error message.
  • Verify the email provider logs for the send attempt.

API reference

Workflow action executions are primarily an operational/audit concept. If your environment exposes executions via an API, link it here as an internal-only reference.

Start from these objects:

  • Workflow triggers
  • Workflow actions