Understanding Logs | Zoho Creator Help

Understanding logs

NotesThis help page is for users in Creator 6. If you are in the older version (Creator 5), click here. Know your Creator version.
In a nutshell
Logs help you monitor user access activity and executions in your Creator applications. This includes visibility into record data-related actions, workflows, triggered APIs, and background processes, enabling you to trace execution paths, identify failures, troubleshoot issues, and debug them effectively.
Availability
  1. Logs are available in all plans of Creator.
  2. Super admin and admins can view and search logs in Creator.

1. Overview

Logs in Zoho Creator provide a centralized view of activities occurring within your application. They help in auditing user access activity within apps and analyzing app executions, offering detailed insights into real-time performance and debugging.

There are two tabs that together provide comprehensive oversight of activities in your Creator account:
  1. Access logs - Captures user interactions and actions performed within an app such as viewing records, submitting forms, triggering blueprint transitions, executing a custom API, and more. The IP address of the user device is also automatically captured for each access log entry.
  2. Application logs - Captures system executions such as workflows, Deluge tasks, APIs, page scripts, and more.
Together, these logs provide end-to-end traceability, making it easier to debug issues and audit user actions even across different environments. Each log entry is retained for two months from the time it is added, after which it is permanently removed.

1.1. Dashboard actions

The Logs dashboard provides the following options to help you navigate and manage logs:
  1. Time zone (): Changes the time zone in which log timestamps are displayed.
  2. Time range filter (): Sets the date and time range for the logs shown in both Access Logs and Application Logs.
  3. Sort (): Sorts the logs in the current log tb either from oldest to newest or vice versa.
  4. Search (): Opens the search panel to filter log entries in the current logs tab. The search options differ for access logs and application logs.
  5. Refresh (): Reloads with the latest entries in the current logs tab.
  6. Eye icon (): Lets you choose which additional columns to display for the log entries in the table.
  7. Actions (): Shows the related actions available for a log entry. For access logs, the admin can navigate to the related application logs and vice versa.

2. Access logs

Access logs capture user-level activities performed in the live mode of the application. These logs help you track user interactions with components such as forms, reports, and pages, including the workflows they trigger. They are especially useful for tracking user behavior, auditing actions, and identifying failures at the interaction level.
Column
Description
Possible values
Timestamp
The date and time when the action occurred
Date-time value
Activity
Specific action performed or triggered by a user

The following app-level actions are recorded in access logs for each component:

Form

  • access_form

  • add_record

  • click_button_in_stateless_form

Report

  • view_report

  • view_record

  • edit_record

  • delete_record

  • duplicate_record

  • export_report

  • import_report

  • print_report

  • add_record_comment

  • delete_record_comment

  • trigger_custom_action_in_report

Page

  • view_page

  • click_actionable_page_elements

  • print_page

  • export_page

Form Workflow

  • enter_field_input

  • execute_form_workflow_on_load

  • add_subform_row

  • delete_subform_row

Schedule Workflow

  • execute_form_schedule

  • execute_custom_schedule

Approval Workflow

  • approve_record

  • reject_record

  • recall_record

Payment Workflow

  • payment_callback

Blueprint

  • trigger_blueprint_transition

Batch Workflow

  • execute_pre_batch_action

  • execute_batch_workflow

  • execute_post_batch_action

Script Execution in Edit Mode

  • execute_script_in_edit_mode

API

  • edit_record_by_id

  • delete_record_by_id

  • get_record

  • get_record_by_id

  • upload_file

  • upload_file_to_subform

  • download_file

  • download_file_from_subform

  • get_fields

  • get_forms

  • get_reports

  • get_pages

  • get_sections

  • get_applications

  • create_bulk_read_job

  • get_bulk_read_job_status

  • download_bulk_read_result

  • create_bulk_insert_job

  • get_bulk_insert_job_status

  • download_bulk_insert_result

  • upload_file_to_bulk_insert_job

  • start_abort_bulk_insert_job

  • execute_custom_api

Application Link Name
The link name of the application where the action occurred
-
Component Link Name
The link name of the involved component in the action
Link name of form, report, page, custom API, and more
Tags
Extra details that apply only to a specific activity in the log entry
  1. form
  2. field
  3. subform_field
  4. form_button
  5. report
  6. report_button
  7. page_element
  8. transition
  9. approval_level
  10. job_id
Record ID
The ID of the record involved
System-generated record ID
Environment
The specific environment where the action occurred
  1. development
  2. stage
  3. production
User Type
Type of user who has triggered the action
  1. account_users
  2. public_users
  3. portal_users
Duration
Time taken to complete the action
ms, seconds, minutes
Trigger Type
Defines how an action was triggered
  1. user_action - App actions triggered manually by a user within the application.
  2. api - App actions triggered by automated API requests such as REST API and custom API tasks.
  3. schedule - Planned operations such as schedule workflows and scheduled batch workflows.
  4. edit_mode_action - Actions triggered from the edit mode of the application, such as running a script while building or testing.
User Email Address
Email address of the user performing the action
Valid email address
Error Code
The error code identifies the specific error that occurred during the request, originating either from the system or an external service involved in the execution.
System or external error code
Error Message
A brief description of the outcome, indicating the details of the error encountered.
-
IP Address
IP of the user device from which the action was triggered
IPv4 or IPv6 value
Component Type
Type of component involved in the action
  1. form
  2. report
  3. page
  4. form_schedule
  5. custom_schedule
  6. approval_workflow
  7. payment_workflow
  8. blueprint
  9. batch_workflow
  10. report_workflow
  11. function
  12. custom_api
HTTP Status Code
The HTTP status code indicates the outcome of the request, reflecting whether it was successfully processed or encountered any specific error.
  1. 200 - ok
  2. 201 - created
  3. 400 - bad_request
  4. 401 - authorization_error
  5. 403 - forbidden
  6. 404 - not_found
  7. 405 - method_not_allowed
  8. 408 - request_timeout
  9. 409 - conflict
  10. 422 - unprocessable_entity
  11. 429 - too_many_requests
  12. 500 - internal_server_error
  13. 501 - not_implemented
  14. 502 - bad_gateway
  15. 503 - service_unavailable
  16. 504 - gateway_timeout

2.1. Viewing access log details

Clicking on an access log entry may display two tabs:
  1. Access Log Summary - A detailed view that provides a structured breakdown of the target activity. This view is organized into multiple sections and all applicable information related to a specific access log will be displayed accordingly:
    1. Overview: Displays key information such as timestamp, activity, trigger type, and the related record IDs.
    2. Component Details: Provides information such as the application link name, component link name, component type, and environment in which the activity happened if the application has been added to environments. Apart from these details, a set of tags are also displayed with more details if applicable for the activity shown.
    3. User Details: Includes the user’s name, email address, user type, role, and permissions to help identify who performed the action.
    4. Execution Details: Provides the outcome of the activity, including its duration, HTTP status, error code, error message, and the unique access log ID that identifies this specific log entry.
    5. Request Details: Captures technical context such as device type and IP address.
    6. Additional Details: Displays contextual information specific to the activity performed. For example, an export shows the report criteria, export format, and record count, and an API call shows the method used.
  2. Workflow Logs - If the access log entry has triggered any workflows, this tab is available with a list of application logs that were triggered.
This detailed breakdown enables precise troubleshooting by correlating user actions with the behavior of the components they trigger.

Navigating to related app log from an access log entry:

1. Hover over the required access log entry and click the ellipsis icon () at the end of that entry.
2. Click View Application Log to navigate to the related app log of that access log entry.

2.2. Additional details displayed for specific log scenarios

Besides the standard sections, the detailed view of certain access logs shows a new section with specific details related to the action performed.
Log Scenario
Label
Possible values
export_report
Report Criteria - Filter criteria applied to the report at the time of export
-

ePHI Fields - Fields containing electronic protected health information that were included in the export
Field link names

PII Fields - Fields containing personally identifiable information that were included in the export
Field link names

Export Format - File format of the exported data
File format such as .xlsx, .pdf, .html, .xml, .json, .csv, and .tsv

Record Count - Number of records exported from a report
-
import_report
File Name - The name of the file being imported
-

File Type - File format of the imported data
.xls, .xlsx, .xlsm, .csv, .tsv, .ods, .mdb, .accdb, .json, and .numbers file formats

Success Count - Number of records imported
-

Failure Count - Number of records that failed during import
-
api
Method - HTTP method used in the API request
GET, POST, PATCH, DELETE

Service Name - The internal or external service involved in the API call
Service name
payment_callback
Transaction ID - Unique ID of the payment transaction
Transaction ID value generated by Zoho Checkout

Payment Gateway - External gateway through which the payment was processed
External payment gateway name
  1. create_bulk_insert_job
  2. upload_file_to_bulk_insert_job
  3. start_abort_bulk_insert_job
Total Records - Total number of records submitted for processing
-

Success Records - Number of records processed
-

Failed Records - Number of records that failed to process
-

Unprocessed Records - Number of records not processed
-
execute_batch_workflow
Batches Succeeded - Number of batches completed in a batch workflow
-

Batches Failed - Number of batches that failed in a batch workflow
-

2.3. Searching and filtering access logs

To find specific access logs, use the filters in the Search Logs panel:
  1. Navigate to Operations in the left pane of the Zoho Creator homepage and click Logs in the Applications section. The Access Logs tab will be opened by default.
  2. Click the search icon () on the toolbar.
  3. Set the required search filters in the Search Logs panel that appears and click Search.
The filtered access log entries are updated in the quick view with the applied filters displayed above the table as chips.
To remove the search filter:
  1. Click the X icon () on the filter chip that is displayed above the log entries table to remove an applied filter.
Available filters:
Overview
Component details
User details
Execution details
Overview
  1. Activity
  2. Trigger type
  3. Record ID

Component details
  1. Application link name
  2. Environment
  3. Component type
  4. Component link name
  5. Tags

User details
  1. User email address
  2. User type
  3. IP address
Execution details
  1. Duration: select a condition, enter a value, and choose a unit.
  2. HTTP status code
  3. Error code
  4. Access log ID
Points to note while searching access logs
  1. Trigger type: Shows only the trigger types applicable to the selected activity.
  2. Component type: Displays only the component types applicable to the chosen trigger type.
  3. Component link name: Select the application link name and component type first. The options shown are limited to components of that type in that application.
  4. Tags: Select the component link name first. The available tags depend on the chosen application link name and component link name.
  5. Report button tag: The report in which the button was clicked is mandatory. When you select this tag, a row for the report is added automatically. Enter the report link name to proceed.

3. Application logs

Application logs capture system executions triggered by end-user's access activities or automated processes. They provide deeper visibility into workflows, Deluge scripts, integrations, and more. These logs are primarily used for debugging failures, analyzing execution flows, and understanding how different processes are executed behind the scenes.
Column
Description
Possible values
Timestamp
Date and time of execution
-
Workflow Link Name
Link name associated with the triggered workflow
Workflow link name
Application Link Name
Link name of the application in which the action execution occurred
App link name
Component Link Name
Link name of the component associated with the execution
Form, report, or page link name
Category
Broader classification of system executions that are recorded in application logs
  1. workflow - Executions of workflows triggered by actions in your application, such as form events, schedules, and approvals.
  2. task - Executions of individual tasks run within a workflow, such as API calls, SMS, and email.
Subcategory
Classification that further identifies the type of execution within a category
The two log categories include the following components:
  1. workflow - form_workflow, schedule_workflow, approval_workflow, payment_workflow, report_workflow, blueprint, batch_workflow, function, and page_script
  2. task - web_data and notification
Event
Name of the executed workflow event or Deluge task
Workflow name or Deluge task:
  1. on_create_form_load
  2. on_create_field_input
  3. on_create_form_submit_validation
  4. on_create_form_submit_success
  5. on_create_addition_of_a_row
  6. on_create_deletion_of_a_row
  7. on_edit_form_load
  8. on_edit_field_input
  9. on_edit_form_submit_validation
  10. on_edit_form_submit_success
  11. on_edit_field_update
  12. on_edit_addition_of_a_row
  13. on_edit_deletion_of_a_row
  14. on_create_edit_form_load
  15. on_create_edit_field_input
  16. on_create_edit_form_submit_validation
  17. on_create_edit_form_submit_success
  18. on_create_edit_addition_of_a_row
  19. on_create_edit_deletion_of_a_row
  20. on_delete_record_delete_validation
  21. on_delete_record_delete_success
  22. form_schedule
  23. custom_schedule
  24. approve_record
  25. reject_record
  26. click_report_button
  27. successful_payment
  28. failed_payment
  29. trigger_blueprint_transition
  30. click_button_in_stateless_form
  31. render_html_snippet
  32. render_zml_snippet
  33. integration_task
  34. invoke_url
  35. invoke_api
  36. sms
  37. email
  38. execute_page_script
  39. initiate_batch_workflow
  40. execute_batch_workflow
  41. successful_batch_workflow
  42. failed_batch_workflow

  43. execute_function

Status
The status indicates the outcome of the request, reflecting whether it was successfully processed or failed to execute.
  1. success
  2. failure
Duration Time taken for execution ms, seconds, minutes
Service
The service from or in which the action is executed
The name or web address of the external or internal service involved in the event.
Message
A brief description of the outcome, indicating either the successful completion of the request or details of the error encountered.
Informational or error messages
Error Code
The error code identifies the specific error that occurred during the request, originating either from the system or an external service involved in the execution.
Internal or external error code
Record ID
The ID of the record involved
System-generated record ID
Component Type
Type of component involved in the action
  1. form
  2. page
  3. form_schedule
  4. custom_schedule
  5. approval_workflow
  6. payment_workflow
  7. blueprint
  8. batch_workflow
  9. report_workflow
  10. function
  11. custom_api

3.1. Viewing application log details

Clicking on an application log entry opens a detailed view that provides deeper insights into system executions triggered by an access activity or system-triggered event. This view includes two tabs:
  1. Summary
    This tab provides an overview of the selected log, presenting execution-level details in a structured format.
    1. Overview: Displays key information such as timestamp, duration, category, subcategory, execution status, error code, message, and a unique application log ID that can be used to identify this specific execution at any given time. This gives a quick snapshot of the execution outcome.
    2. Component Details: Provides information about the executed event or Deluge task and the application, workflow, and component involved in the execution. It also shows the affected record and the external service or domain called, where applicable.
    3. Execution Details: Conveys details that help establish the context in which the execution occurred and identify the exact workflow or process involved. This section includes information such as the execution status, error codes, and the relevant access log ID of this log trigger.
  2. Task logs
    This tab lists all individual tasks executed as part of the selected workflow. Each entry represents a specific step within the workflow, along with its execution status and related details. This allows you to trace the workflow execution at a granular level and identify exactly where a failure occurred.

Navigating to related access log from an app log entry:

  1. Hover over the required app log entry and click the ellipsis icon () at the end of that entry.
  2. Click View Access Log to navigate to the related access log of that app log entry.
Alternately, the related access log can also be opened from within the detailed view of that app log entry by clicking the View Access Log button at the top right corner.

3.2. Searching and filtering application logs

To search application logs:
  1. Navigate to Operations in the left pane of the Zoho Creator homepage and click Logs in the Applications section.
  2. Navigate to the Application Logs tab.
  3. Click the search icon () on the toolbar.
  4. Set the required search filters in the Search Logs panel that appears and click Search.
The filtered app log entries are updated in the quick view with the applied filters displayed above the table as chips.
To remove the search filter:
Click the X icon () on the filter chip that is displayed above the log entries table to remove an applied filter.
Available filters:
Overview
Component details
Execution details
Overview
  1. Event
  2. Category
  3. Subcategory
  4. Record ID
  5. Service
Component details
  1. Application link name
  2. Environment
  3. Component type
  4. Component link name
  5. Workflow link name
Execution details
  1. Duration: select a condition, enter a value, and choose a unit.
  2. Status
  3. Error code
  4. Message
  5. Access log ID

Points to note while searching app logs
  1. Category: Shows only the categories that apply to the chosen event.
  2. Subcategory: Shows only the subcategories that apply to the chosen category.
  3. Component type: Shows only the component types that apply to the chosen subcategory.
  4. Workflow link name: Select the subcategory and application first. The options shown are limited to workflows of that subcategory in that application.
Note: This filter isn’t available for the page_script, web_data and notification subcategories.

4. Points to note

Logs Retention and Storage
  1. Logs are retained for a fixed period of two months in a Creator account across all plans.
  2. Logs count toward your account’s Audit & Logs Storage, which can be checked under Billing > Usage Details. Once this storage is full, logging is paused and new activities and events are not recorded.
Privacy
  1. The IP address of the user triggering an action within an application is logged by default. Hence, ensure all users in your Creator account are aware that data such as their IP address, user details, and other access details are collected during application usage.
Log Accessibility
  1. The related access log can be viewed directly from an app log to trace how it was triggered.
  2. The related application logs can be viewed directly from an access log entry to trace the workflows it triggered.

5. Related topics

  1. Understanding audit trail
What's next
What's next
Learn about audit trail in Zoho Creator that allows you to track changes made to your application data, including who changed what and when.