> ## Documentation Index
> Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation FAQ

> AI Table automation FAQ: who can configure automations, how run counts are calculated, the 7-day log window, why the automation entry may be hidden, group limits per step, and other common operational questions.

<AccordionGroup>
  <Accordion title="Who can configure or modify automations?">
    AI Table owners / admins / editors (with advanced permissions off, or with manage-all-tables permission via advanced permissions) can enable or modify automations. If a user loses these permissions, automations they enabled stop running — an owner / admin / editor can re-enable them.
  </Accordion>

  <Accordion title={`Why doesn't "When a record is created" trigger fire?`}>
    **Note:** clicking **New** creates a blank row — every field is empty. If a downstream action references any non-system field (i.e. anything other than Created by / Last modified by / Created time / Last modified time) from the just-created record, the value is actually empty and the action will error out.
  </Accordion>

  <Accordion title="How far back can I see run logs?">
    Up to 7 days.
  </Accordion>

  <Accordion title="Why don't I see the automation entry?">
    Possible reasons:

    * You only have read permission on the AI Table.
    * You have automation edit permission but advanced permissions block you from manage-all-tables.
    * You are not in the current organization.
  </Accordion>

  <Accordion title="How many automations can I create per AI Table?">
    Unlimited.
  </Accordion>

  <Accordion title="What's the run-count cap on automations?">
    See the link below for details. Once the monthly cap is hit, runs stop and resume on the 1st of the next month at 0:00 GMT+0.

    [Billing model — DingTalk Open Platform](https://open.dingtalk.com/document/connector/connection-platform-billing-model#5adcd8504dk8w "Billing model — DingTalk Open Platform")

    **Tips for connection-flow node usage:**

    * Delete unused execution nodes, or use branches to avoid pointless calls.
    * In loops, add condition checks to skip unnecessary iterations.
    * Use the platform's alert subscription to get notified on failures.
    * Disable invalid connection flows to stop wasting runs.
  </Accordion>

  <Accordion title="How is automation run count calculated?">
    **Counted**

    * Successful action node — 1.
    * **Delay** node call — 1.
    * **HTTP request** node call — 1.
    * **Branch** node — 1 per evaluation.
    * **Loop** node iterates within one workflow run — a loop with one node iterating 200 times counts as 200.
    * When a query returns nothing, it still counts as a successful run (e.g. directory queries with no matches still count as 1).

    **Not counted**

    * Trigger event execution.
    * Skipped nodes; failed nodes.
    * Debug runs.
  </Accordion>

  <Accordion title="How do I check this month's run count?">
    Open **Workflow management** to see the org's accumulated node runs for the current month.
  </Accordion>

  <Accordion title="Can I include links in automated messages?">
    Yes. In **Send message to user or group**, configure **bottom-of-card buttons** with custom labels and target URLs.
  </Accordion>

  <Accordion title="What identities can send automation messages?">
    **User account** or **Doc automation assistant**.
  </Accordion>

  <Accordion title="Max groups per node (step) in one automation?">
    5.
  </Accordion>

  <Accordion title="Max recipients when notifying members of a group?">
    100. The chat blocks beyond that, but the run shows success.
  </Accordion>

  <Accordion title="Max groups per whole automation?">
    10.
  </Accordion>

  <Accordion title="If we hit the monthly cap, do org-wide automations stop immediately?">
    No — there's a 5-day grace period.
  </Accordion>

  <Accordion title="Recipient caps when sending as user account?">
    Up to 20 individual chats and up to 5 groups per call. Up to 200 individual messages per minute.
  </Accordion>

  <Accordion title="Can I pick formula or lookup fields in automation?">
    Yes — supported.
  </Accordion>

  <Accordion title="How long are automation execution records kept?">
    Up to 1 month.
  </Accordion>
</AccordionGroup>