Logging
Logs are detailed notes written while an automation step is running.
They help you understand what the step tried to do, what worked, what failed, and what happened right before a problem.
The Basic Idea
What a Log Entry Tells You
| Part | Meaning |
|---|---|
| Time | When the message happened |
| Level | How important the message is |
| Message | What happened |
| Step | Which part of the automation wrote the message |
You usually do not need to read every log line. Start with warnings and errors, then look at the messages just before them.
Log Levels
| Level | Meaning | How to treat it |
|---|---|---|
ERROR | Something went wrong | Start here when a run fails |
WARN | Something may need attention | Review it, especially if it repeats |
INFO | Normal progress update | Useful for understanding what happened |
DEBUG | Extra detail for investigation | Use only when troubleshooting |
Examples in Plain Language
| Message | What it means | What to do |
|---|---|---|
| Connection timeout | The step waited but the other system did not respond | Retry or check the external system |
| Authentication failed | The step could not sign in | Check credentials or permissions |
| No data returned | The request worked but found no matching data | Check filters, dates, or source data |
| Rate limited | The other system asked the automation to slow down | Use a retry with a longer wait |
| File not found | The step could not find the expected file | Check the file path or previous step |
How to Use Logs When a Run Fails
What to Look For
| Clue | What it may mean |
|---|---|
| Error appears immediately | Setup, permission, or missing input issue |
| Error appears after a long wait | Timeout or slow external system |
| Warning appears before the error | The warning may explain the root cause |
| Same error appears in many runs | Configuration or external system issue |
| Error appears after a previous step produced empty output | The failed step may not have received the data it needed |
Debug Mode
Debug mode shows extra detail for troubleshooting.
Use it when:
- A step fails but the normal error is not clear
- You need to confirm which input values are being used
- You are checking why a step is slow
- An administrator or support person asks for more detail
Avoid leaving debug mode on all the time. It can create many extra log messages and may show details that are not useful for everyday monitoring.
Reading Logs Without Getting Lost
Start with this order:
- Open the failed run.
- Find the first failed step.
- Filter to
ERRORmessages. - Read the messages just before the first error.
- Check
WARNmessages if the error is unclear. - Compare with a recent successful run if needed.
Log Patterns
| Pattern | What it usually means |
|---|---|
| Ends with success | The step completed normally |
| Warning followed by retry | A temporary issue happened and the system tried again |
| Warning followed by success | The step recovered |
| Error with no retry | The step failed and stopped |
| Long gap between messages | The step may have been waiting on another system |
Sensitive Information
Logs should help troubleshooting without exposing private information.
Avoid putting these in logs:
- Passwords
- API keys
- Secret tokens
- Full credit card numbers
- Sensitive customer data
- Private personal information
If sensitive information appears in logs, treat it as a security issue and contact the system owner.
Good Logging Habits
Use clear step names
Good step names make logs much easier to understand.
Look for the first error
Later errors may only be side effects of the first problem.
Use timestamps
Long gaps can show where the automation waited or slowed down.
Save useful error messages
If you need help, share the failed step name, time, and error message with the owner or support team.
Watch repeated warnings
A warning that repeats often may become tomorrow's failure.
Related Pages
- Monitoring Automations - how to find the failed run and step
- Retry Strategies - how retries appear in logs
- Concurrency Control - how overload can show up as timeouts or slow logs