Invoking & Logs
Learn about Invoking & Logs in WaymakerOS.
Monitor your ambassador's execution history, manually trigger runs, and debug issues using the invocation log.
Viewing invocation logs
Open your ambassador's detail page and click the Invocations tab. Each entry shows:
- Timestamp — when the invocation started
- Duration — how long it took to complete
- Status — success, failed, or timeout
- Input — the data sent to the function
- Output — the data returned
Status indicators
| Status | Meaning |
|---|---|
| Success | The function completed without errors |
| Failed | The function threw an error or returned an error response |
| Timeout | The function exceeded the maximum execution time |
Manual invocation
To test an ambassador without waiting for its schedule:
- Open the ambassador detail page
- Click Invoke (or use the MCP tool
host-ambassador-invoke) - Optionally provide input data
- The function runs immediately and the result appears in the invocation log
This is useful for testing new code, debugging, or running a one-off job.
AI credit usage
If your ambassador uses One AI or Edge AI, credit usage is tracked automatically. Each invocation log entry includes:
- Model used — which AI model processed the request
- Tokens consumed — input and output token counts
- Credit cost — how many credits were charged
Edge AI credits are logged asynchronously — they may appear a few seconds after the invocation completes. All AI usage counts against your organization's WaymakerOne Pass allocation.
Viewing logs
From the ambassador detail page, access runtime logs that show:
- Console output from your function
- Error messages and stack traces
- External API call results
- Timing information
Use the MCP tool host-ambassador-logs or the CLI to stream logs in real time.
Debugging common issues
Function timeout
If your ambassador times out:
- Check if it's waiting on a slow external API
- Break long-running tasks into smaller steps
- Increase the timeout limit in settings (if available)
Authentication errors
If your ambassador can't access external services:
- Check environment variables are set correctly
- Verify API keys haven't expired
- Ensure the authentication mode matches the external service's requirements
Data not appearing
If your ambassador writes to a table but data doesn't show:
- Check the ambassador's Connected Tables panel to confirm the table connection is declared
- Verify the access level is "Write" or "Read-Write"
- Check the invocation log for error responses
Next steps
- Creating Ambassadors — set up a new ambassador
- Serverless Functions — ambassador overview
- Introduction to Monitor — platform-wide health
- Activity Feed — all operational events