How to Check Bot Error Logs in ZazzyAgent
Sometimes a flow doesn't behave the way you expect.
A message doesn't send.
An API call fails.
A JSON response causes an error.
A flow stops at a particular step.
Instead of guessing which part is broken, check the Bot Error Logs.
The current platform provides an error-log area that records flow-related errors and provides information such as the error message and time, with an option to jump back to the affected flow.
What are Bot Error Logs?
Bot Error Logs show errors generated during automation execution.
They help answer:
What went wrong?
and:
When did it happen?
They can be especially useful for technical flow problems involving APIs, JSON, URLs and other configured components.
Why should you check the logs?
A customer saying:
The bot isn't working.
doesn't tell you where the problem is.
The error log may show something specific such as:
JSON Decode Error
or:
403
That immediately gives you a direction for troubleshooting.
Open Bot Error Logs
Open the relevant Bot Manager area.
Find the options menu.
Open:
Bot Error Logs
The exact placement may vary with the current dashboard, but the error log is available from the bot-management options.
What information can you see?
The current error log provides information such as:
Error number
Error message
Error time
Action/edit option
The error message is the most important part when diagnosing a problem.
Use the timestamp
The time of the error helps you match the log entry to a specific customer interaction.
For example:
Customer reported a problem at 3:05 PM.
Find the error around:
3:05 PM.
This can identify the failed flow execution.
Open the affected flow
Where the error entry provides an edit/jump option, use it to return to the flow that generated the error.
The current error-log interface provides a way to jump directly to the relevant flow from an error entry.
Common error: JSON Decode Error
This usually means ZazzyAgent received data that wasn't valid JSON or wasn't in the expected format.
A common place to investigate is:
HTTP API
JSON-based integration
External data
Dynamic-list data
Check the actual response/request structure.
Common error: 403
A 403 error generally indicates that access was denied.
Possible causes include:
Authentication
Permission
Expired credential
Restricted URL
Check the external system and credentials.
Common error: 404
A 404 usually means the requested URL/resource wasn't found.
Check:
API URL
Webhook URL
Resource ID
Endpoint path
A small URL mistake can cause this.
Error logs and API troubleshooting
If an API flow isn't working:
Don't immediately rebuild the flow.
First check:
Bot Error Logs
↓
Exact error
↓
Affected flow
↓
API configuration
This gives you evidence instead of guessing.
Error logs and custom variables
When a flow depends on dynamic customer data, also inspect the values being used.
For example:
order_id
customer_id
membership_status
If one of these values is missing or incorrect, the subsequent API call may fail.
The current debugging tools also expose per-user custom variables that can help when diagnosing dynamic data.
Error logs vs customer support
If a customer reports:
The bot didn't reply.
the error log tells you whether the platform recorded an execution error.
If there is no relevant error, investigate other causes such as:
Trigger wasn't matched
Flow wasn't active
Message wasn't received
Channel-level issue
Routing issue
Don't assume that every missing reply creates an error-log entry.
Don't clear logs immediately
The error log is useful evidence.
Don't clear it before investigating active problems.
The current platform provides a Clear Log action, but clearing removes the visible error history.
Investigate first.
Use a fresh test after fixing
After changing the flow:
Save the flow.
Trigger it again.
Check whether the problem occurs.
Check the error log again.
You want to know whether the same error reappeared.
Example: Broken API URL
Customer:
Check my order.
Flow:
User Input
→ Order Number
→ HTTP API
→ Error.
Open logs.
You see:
404
Check the API endpoint.
You discover the configured URL has the wrong path.
Fix it.
Run the test again.
Example: Invalid JSON
Your API returns something unexpected.
The log shows:
JSON Decode Error.
Check the external response.
You discover the response isn't valid JSON.
Fix the external API response or the parsing/mapping configuration.
Example: Missing authentication
The external server returns:
403
Check the authentication configuration.
Confirm the credential and permissions.
Then test again.
Use logs alongside normal testing
Don't rely only on the error log.
Use both:
Customer test
Flow inspection
Error logs
This gives you a much clearer picture.
A practical troubleshooting process
When a flow fails:
Step 1
Reproduce the problem.
Step 2
Record the approximate time.
Step 3
Open Bot Error Logs.
Step 4
Find the matching error.
Step 5
Read the exact error message.
Step 6
Open the affected flow.
Step 7
Fix the relevant component.
Step 8
Run the test again.
Step 9
Confirm the error no longer appears.
Keep the problem specific
Instead of saying:
The bot is broken.
Try to identify:
The HTTP API call returns 403.
or:
The flow produces a JSON Decode Error.
Specific errors usually lead to specific fixes.
The core idea
Bot Error Logs are the platform's evidence trail for flow execution problems.
When an automation behaves unexpectedly:
Check the evidence before changing the automation.
That one habit can save a lot of unnecessary rebuilding.