Skip to main content

Run History

Time to learn: 5 minutes
Prerequisites: None - available for all automations

Run history shows you a complete log of all document generation executions. Track what happened, when it happened, and whether it succeeded or failed.

📊

Run History Quick Reference

ViewExecution History button
FilterBy status, date, outcome
SearchIn execution logs
DetailsExpandable rows

What Is Run History?​

Run history is a log of every time your automation runs. It shows:

  • When documents were generated
  • Which records were processed
  • Success or failure status
  • Execution details and logs
  • Performance metrics (duration, etc.)

Why Use Run History?​

Run history helps you:

  • Track executions - See when documents were generated
  • Debug issues - Find out why something failed
  • Monitor performance - See how long generation takes
  • Audit activity - Keep records of what was generated

Viewing Run History​

  1. Click the "Execution History" button in your automation
  2. You'll see a list of all executions
  3. Click on any execution to see details

Execution Information​

Each execution shows:

Basic Information​

  • Execution ID: Unique identifier for this run
  • Timestamp: When the execution started
  • Duration: How long it took to complete
  • Status: Success, failure, or partial

Status Types​

  • Success: All documents generated successfully
  • Failure: Execution failed (check logs for details)
  • Partial: Some documents succeeded, some failed

Trigger Information​

  • Triggered by: Manual, scheduled, webhook, API, etc.
  • Trigger details: Information about what started the execution

Execution Logs​

Detailed logs show:

  • Processing steps: What Gdocify did during execution
  • Record processing: Which records were processed
  • Errors: Any errors that occurred
  • Warnings: Non-critical issues

Filtering and Searching​

Filter by Status​

Filter executions by:

  • All: Show all executions
  • Success: Only successful executions
  • Failure: Only failed executions
  • Partial: Only partial successes

Search in Logs​

Search execution logs for:

  • Specific record IDs
  • Error messages
  • Keywords
  • Timestamps

Sort Options​

Sort executions by:

  • Date: Most recent first or oldest first
  • Duration: Fastest or slowest
  • Status: Group by success/failure

Understanding Execution Status​

Success​

All documents were generated successfully:

  • ✅ All records processed
  • ✅ All documents created
  • ✅ All actions completed (emails sent, webhooks called, etc.)

Failure​

Execution failed completely:

  • ❌ No documents generated
  • ❌ Check logs for error details
  • ❌ May need to fix configuration or data

Partial​

Some documents succeeded, some failed:

  • ⚠️ Some records processed successfully
  • ⚠️ Some records failed
  • ⚠️ Check logs to see which records failed and why

Performance Metrics​

Track performance over time:

Duration​

See how long executions take:

  • Fast executions: Under a few seconds per document
  • Slow executions: May indicate performance issues
  • Trends: Watch for increasing duration over time

Success Rate​

Monitor success rates:

  • High success rate: Most executions succeed
  • Low success rate: May indicate configuration issues
  • Improving trends: Success rate increasing over time

Troubleshooting with Run History​

Finding Errors​

  1. Filter by "Failure" status
  2. Click on failed executions
  3. Review error logs
  4. Identify the issue
  5. Fix the problem
  6. Re-run the execution

Understanding Failures​

Common failure reasons:

  • Data issues: Missing or invalid data
  • Template issues: Problems with placeholders or sections
  • Permission issues: Can't access data or save files
  • Network issues: Connection problems
  • Rate limits: Exceeded API limits

Re-running Executions​

If an execution failed:

  1. Review the error logs
  2. Fix the issue
  3. Re-run the execution
  4. Monitor the new execution

Best Practices​

Regular Monitoring​

  • Check regularly: Review run history periodically
  • Watch for trends: Look for patterns in failures
  • Monitor performance: Track execution duration
  • Review logs: Check logs for warnings or errors

Debugging​

  • Start with failures: Focus on failed executions first
  • Read error messages: Error messages explain what went wrong
  • Check data: Verify data source has correct data
  • Test fixes: After fixing, test with a small batch

Documentation​

  • Note issues: Document recurring problems
  • Track fixes: Keep notes on what fixes worked
  • Share knowledge: Share solutions with your team

Tips​

  • Review regularly: Check run history at least weekly
  • Act on failures: Don't ignore failed executions
  • Monitor trends: Watch for patterns over time
  • Use filters: Filter to find specific executions quickly
  • Learn from logs: Logs contain valuable debugging information

Common Questions​

"Why did my execution fail?"​

Check the execution logs for error messages. Common causes:

  • Missing data in data source
  • Invalid placeholder mappings
  • Permission issues
  • Network problems

"How long should executions take?"​

It depends on:

  • Number of records
  • Document complexity
  • Network speed
  • API response times

Typically, 1-5 seconds per document is normal.

"Can I re-run a failed execution?"​

Yes! After fixing the issue, you can trigger a new execution. The run history helps you identify what needs to be fixed.

Next Steps​

Now that you understand run history:

  1. Learn about Troubleshooting for common issues
  2. Explore Triggers to automate generation
  3. Check out Result Configuration for output settings