Skip to main content
  • 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.
  • 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.
  • How far back can I see run logs? Up to 7 days.
  • 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.
  • How many automations can I create per AI Table? Unlimited.
  • 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 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.
  • 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.
  • How do I check this month’s run count? Open Workflow management to see the org’s accumulated node runs for the current month.
  • 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.
  • What identities can send automation messages? User account or Doc automation assistant.
  • Max groups per node (step) in one automation?
  • Max recipients when notifying members of a group?
    1. The chat blocks beyond that, but the run shows success.
  • Max groups per whole automation?
  • If we hit the monthly cap, do org-wide automations stop immediately? No — there’s a 5-day grace period.
  • 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.
  • Can I pick formula or lookup fields in automation? Yes — supported.
  • How long are automation execution records kept? Up to 1 month.