Troubleshooting Automations
Find the error message or symptom below, then follow the recovery steps. Errors specific to one block are also listed on that block's page under Triggers or Steps.
Connection problems
The Neon Deer connection is added on the app's Connections tab in Attio (see Setup). Every trigger and step needs it, and it needs a Neon Deer account (see What needs a Neon Deer account).
| You see | What it means and what to do |
|---|---|
This Neon Deer account can't use Advanced Automations yet. Contact Neon Deer support to enable it, then connect again. | Shown when you add the connection. The Neon Deer account does not have Automations enabled. Contact Neon Deer support, then add the connection again. |
Couldn't reach Neon Deer to verify this connection. Please try connecting again in a moment. | Neon Deer could not be reached while the connection was checked. Try again shortly. |
Neon Deer isn't connected. Sign up at app.neondeerdata.com, then open Workflow Utilities in your Attio workspace settings (Apps) and connect Neon Deer. (a step, the Schedule in workflow dialog or the Find lookup table row table picker) | No workspace connection exists. Create a Neon Deer account if you have none, then add the connection on the Connections tab. |
Neon Deer is not connected (app settings page) | No workspace connection exists. Add one on the Connections tab. |
Your Neon Deer connection needs attention (app settings page) | Either the access token expired, so check the connection's access-token refresh schedule on the Connections tab, or access was revoked, so remove the connection and add it again. |
Neon Deer is setting up your account (app settings page) | Setup is still running. It usually takes a few seconds; the page checks again every 5 seconds. |
We couldn’t confirm your setup (app settings page) | The status check failed; the error is shown with it. Reload the page, and contact Neon Deer support if it persists. |
Neon Deer not connected (Scheduled runs widget) | The widget needs the connection. Add it on the Connections tab. |
A workflow will not turn on: Sign up for Neon Deer at app.neondeerdata.com, then open Workflow Utilities in your Attio
workspace settings (Apps), connect Neon Deer, and turn the workflow on. | Every trigger needs the connection. Add it, then turn the workflow on again. For Scheduled record, if the connection exists, the message says Neon Deer could not set up scheduling or names the plan or account problem; fix that and try again. |
Removing the connection in Attio also cancels pending scheduled runs if the removal reaches Neon Deer; see Canceling.
Permissions
Roles on the Neon Deer platform come from your Neon Deer workspace membership. An Attio role does not grant anything on the platform.
| Action | Who can do it |
|---|---|
| View, edit, import or export lookup tables |
A workspace admin, or a member with Manage Advanced Workflow Automations. Others see An app admin can
manage lookup tables. |
| View and cancel scheduled runs | Any workspace member |
| View the Overview and Activity tabs | Any workspace member |
| Run task trigger setup again | A workspace admin, or a member with the app permission |
| Add or remove the Neon Deer connection | Done in Attio, on the app's Connections tab |
A step can also be refused before it runs. Every block checks the workspace's Neon Deer access first. Without a connection, a step
fails with Neon Deer isn't connected. Sign up at app.neondeerdata.com, then open Workflow Utilities in your Attio workspace settings (Apps) and connect Neon Deer. With a connection, blocks keep running during Neon Deer outages and after the connection's access token
expires. A block is refused when Neon Deer reports that access is blocked or revoked or that account setup failed, or when the app
cannot read its stored status and gets no clear answer. A refused step fails with Neon Deer didn't allow this step for this
workspace. If the Neon Deer connection was removed or revoked, remove and re-add it under Workflow Utilities in your Attio workspace
settings (Apps); otherwise check your account at app.neondeerdata.com. A refused trigger starts no run. The refusal is kept
until a later status check succeeds.
Failed steps
-
A failed step returns a message and a retryable flag. The app itself does not retry. Errors from Attio's API start with
Attio HTTP <status> <METHOD> <path>, followed by Attio's status text and, when Attio sends them,
its error type and code. Network failures read Network error calling Attio: <message>.
-
Attio 429 (rate limit) and 5xx errors and network errors are marked retryable: run the workflow again later, after checking which
steps already completed (see Recovery steps). Other errors are not
retryable, except those marked retryable in the Find lookup table row table below; fix the configuration or data first.
-
Nothing found is not a failure. Find notes, Find tasks, Find workspace member, Find lookup table row, Get meeting, Get comment and
Get thread report Count 0 or Found false. Branch on that output instead of expecting an error. Convert value reports bad input on
its Invalid input branch.
- Fail workflow always ends the run with its own message, by design.
- Messages specific to one step are listed on that step's page.
Find lookup table row errors
Cause Retryable Message No connection No Neon Deer isn't connected. Sign up at app.neondeerdata.com, then open Workflow Utilities in your Attio workspace settings (Apps) and connect Neon Deer.Connection token expired No The Neon Deer connection's access token expired. Ask an admin to check its refresh schedule in Attio.Plan does not include lookup tables No Your Neon Deer plan doesn't include lookup tables. Upgrade in Neon Deer → Settings → Billing. See Settings → Billing in Neon Deer.Payment overdue No Your Neon Deer payment is overdue. Update it in Neon Deer → Settings → Billing.Lookup tables not enabled for the account No Lookup tables aren't available on your Neon Deer account yet. Contact Neon Deer support.Account setup failed No Neon Deer couldn't finish setting up your account. Contact Neon Deer support.Connection lacks access No This connection cannot read Neon Deer tables. Ask an admin to review the connection and workspace access.Table or field not chosen No Choose a table and lookup field in this step.Table archived or deleted, or lookup turned off No The selected table or lookup field is no longer available. Choose it again in this step.Value of the wrong type No Provide a value of the selected field's type in this step.Value refused by Neon Deer No The lookup value is not valid for the selected field. Check this step's inputs.App cannot read Attio objects (record lookups) No This app cannot read Attio objects. Ask an admin to review its permissions.Record object no longer in Attio (record lookups) No An Attio object used by this lookup is no longer available. Review the table and this step.Attio did not list objects within 5 seconds (record lookups) Yes Attio took too long to respond. Retry shortly.Invalid or unexpected response No Neon Deer returned an invalid table response. Contact Neon Deer support.Table changed during the run Yes The table changed while this step was running. Retry shortly.Rate limited Yes Neon Deer is receiving too many requests. Retry shortly.Account setup not finished Yes Your Neon Deer account is still being set up. Try again in a minute.Neon Deer unavailable (503) Yes Neon Deer is temporarily unavailable. Try again shortly.Temporarily unavailable (other) Yes Neon Deer tables are temporarily unavailable. Retry shortly.Unreachable Yes Neon Deer could not be reached. Retry shortly.No answer in 5 seconds Yes Neon Deer took too long to respond. Retry shortly.Anything else, including other Attio errors while listing objects Yes The lookup could not be completed. Retry shortly.
A lookup that returns Found false is not an error. If you expected a match, check the value against the
matching rules and that the fields you need are shared with workflows.
A trigger did not start a run
Triggers have no error branch and show nothing in the workflow. When something goes wrong inside a trigger, no run starts. Check
these causes:
- The workflow is turned off. Turning it on registers the trigger; turning it off removes it.
-
The item no longer exists in Attio when the trigger reads it, or the read from Attio fails. That event is dropped.
-
The note content and title triggers fire at most once per note every 300 seconds. Further edits to the same note within that
window do not start a run.
-
Created and deleted triggers start at most one run per item each time the workflow is turned on.
-
Task status changed, Task assignee changed and Task deadline changed compare a task with a value stored earlier. The first change the app sees for a
task it has no stored value for is stored and does not start a run; later changes fire normally. With a Neon Deer connection,
turning on a task change trigger asks Neon Deer to prepare stored values for your existing tasks. Its progress shows on the
platform's Automations Overview under
Task triggers, and an admin can run it again; tasks that already have a stored
value are skipped.
- The workspace's access check refused the trigger (see Permissions).
Each trigger's page lists exactly which events it listens to and what it outputs.
Scheduling problems
The Schedule in workflow dialog does not open its form
Message What to do Neon Deer isn't connected. Sign up at app.neondeerdata.com, then open Workflow Utilities in your Attio workspace settings (Apps) and connect Neon Deer.Create a Neon Deer account if you have none, then add the Neon Deer connection on the app's Connections tab. Neon Deer could not be reached. Close this and try again.Close the dialog and try again shortly. Your Neon Deer plan doesn't include scheduled runs. Upgrade in Neon Deer → Settings → Billing.Your plan does not include scheduled runs. See Settings → Billing in Neon Deer. The same message can appear when you schedule records. Scheduled runs need a time zone An admin sets the workspace time zone in Neon Deer under Settings » General. Then try again. No workflow is ready for these records. Turn on a workflow that starts with the 'Scheduled record' trigger for this object, then try again.
Turn on a workflow that starts with Scheduled record for this object. If it was archived and then unarchived, make any
edit and publish it.
Neon Deer refused the records
Message What to do That time has already passed. Choose a later time.Choose a time in the future. Choose a date up to 12 months ahead.Choose an earlier date. Choose a time on a 15-minute mark, like 9:00 or 9:15.Choose :00, :15, :30 or :45. That time can't be scheduled. Choose another time.Choose another time. That workflow is turned off. Turn it on in Attio, then try again.Turn the workflow on, then schedule again. That workflow runs for a different object.Select records of the object the workflow's trigger is set to, or pick another workflow. Your workspace has reached its limit of scheduled runs. Cancel some in Neon Deer, or wait for them to run.The workspace holds 10,000 pending runs at most. Cancel runs you no longer need, or schedule fewer records. Attio did not say who is scheduling these records. Reload the page and try again.Reload the Attio page and try again. Neon Deer did not confirm these records were scheduled. Check a record's Scheduled runs before trying again.The records may have been scheduled anyway. Open a record's Scheduled runs widget before scheduling again, so you do not schedule them twice. Neon Deer could not schedule these records. Try again.Try again.
Scheduled N records, then stopped means one request was refused after earlier ones succeeded: the first N records are
scheduled and the rest are not. A run that was scheduled but ended as Failed or Skipped shows the reason in History; the statuses are
explained under Run statuses.
Limits
Fixed limits, the same on every plan, except where marked.
Limit Value See Notes scanned by Find notes 5,000 (100 pages of 50) Find notes Tasks scanned by Find tasks 5,000 (50 pages of 100) Find tasks Members listed by Find workspace member (by email) 50 pages of 100 Find workspace member Note content and title trigger cooldown 300 seconds per note Note content updated Convert HTML to markdown input 1,000,000 characters Convert HTML to markdown Transcript pages read 50 Get call transcript Folder name 255 characters; longer names are cut Create folder File entries checked on a record 2,000 Create folder Lookup request timeout 5 seconds Find lookup table row Lookup requests 1,200 per 60 seconds per workspace Find lookup table row errors Tables shown per picker search 50 Find lookup table row Text value length 1,000 characters Field types Fields per table 50 Lookup tables Rows per custom table 50,000 Lookup tables Custom tables and rows per workspace Depends on your plan; the Lookup tables page shows usage Lookup tables Table and field names 1 to 80 characters Fields CSV file 1,048,576 bytes; 1 to 2,000 data rows; 1 to 50 columns Import CSV Grid paste 50 rows by 50 columns Editing rows Records per scheduling request 250; larger selections are sent in several requests Large selections Pending scheduled runs per workspace 10,000; a request that would exceed it is refused whole Large selections Scheduling horizon and granularity 12 months ahead; 15-minute marks Which times can be scheduled Late window for a scheduled run 6 hours When the time arrives Send attempts per scheduled run 3 attempts; 10 seconds each When the time arrives Scheduled runs canceled at once on the platform The runs selected on the current page (up to 50), or one batch Canceling Pending runs shown in the record widget 100 Scheduled runs widget Scheduled run history 90 days Scheduled runs tab
Recovery steps
- Read the step's message in the workflow run in Attio. Find it in the tables above or on the step's page. A
retryable error usually clears on its own.
- Before you run the workflow again, check which steps already completed in the failed run. Running the
workflow again runs every step again. Create note creates a second note. Move note copies the
note again if the original was not deleted, and fails with
Source note <id> not found (deleted or wrong ID).
if it was.
- For a connection error, open the app's settings page in Attio. It names the problem: add the connection, check the
token refresh schedule, or remove and re-add the connection.
- For a lookup error, open the step and choose the table and lookup field again if either was archived, deleted or
turned off. Check that the value wired in has the lookup field's type.
- For scheduled runs, check the Scheduled runs tab in Neon Deer. Upcoming shows
Workflow off for runs
whose workflow is off; turn it on before their time, or cancel them. History shows why a run failed or was skipped. To retry a
failed or skipped run, schedule the record again.
- For a trigger that did not fire, confirm the workflow is on and work through
A trigger did not start a run.
- If the problem persists, contact Neon Deer support with the workflow name, the step and the exact message.
For what Neon Deer stores and for how long, see the Privacy Policy.