Use this page when the Workflows screen, the Run Workflow dialog, the runs table, the node window, a run log, the alerts window or the workflow diagram shows a message you did not expect. Find the message, then fix the cause it names.
Some messages say "Metadata" for a workflow, for example Failed to create metadata. They mean the same thing.
When an action fails, the message shows the server's reason under the title when the server sends one. When it does not, the message falls back to its generic text, such as Failed to restart job.
| You see | What it means and what to do |
|---|---|
| Validation Error with a field message | A field is missing or invalid. Fix the field marked in red. |
| Datasource is required | Pick a Datasource. |
| Type is required | Pick Standard or Snapshot as the Workflow Type. |
| Name must be at least 2 characters | Enter a longer Workflow Name. |
| Workflow name cannot contain reserved words: standard, snapshot, replication | Remove the word. It is refused in any capitalisation and even inside another word. Keeping a workflow's existing name when you edit it is allowed. |
| Batch size must be at least 1 | Enter 1 to 100 in Batch Size, since the save accepts at most 100. |
| Retry count must be at least 0 or Retry count cannot exceed 10 | Enter 0 to 10 in Restart Count. |
| Frequency must be at least 1 or Frequency must be between 1 and 100 | Enter 1 to 100 in Frequency. |
| Schedule day must be at least 1 or Schedule day must be between 1 and 31 | Enter 1 to 31 in Schedule Day. |
| End time is required when unit is Minute or Hour | Set End Time. |
| End time must be after start time | Set an End Time later than Start Time. A window cannot run past midnight. |
| Expected number, received nan | A number field is empty. Type a number. |
| Failed to create workflow or Failed to update workflow (toast title) | The server refused the save. The text below the title is its reason when the server sent one. The usual causes are a Batch Size above 100 and a name another workflow uses, so use 100 or less and a unique name. |
| Failed to create metadata, Failed to update workflow or Failed to delete metadata (toast title Error) | The request failed with no reason from the server. Try again, and check your permissions for this workflow type. |
| Metadata created successfully or Metadata updated successfully | The workflow was created or updated. Nothing is wrong; the change shows in the list. |
| Workflow not found | The data source's workflow could not be found when the save ran, usually because it was removed while the dialog was open. Close the dialog and open it again. |
| Metadata not found | The workflow could not be found when the change was saved, for example because it was deleted while the dialog was open. Close the dialog; the change cannot be saved. |
| Workflow cannot be changed. Please create a new sub-workflow instead. | A save tried to move the workflow to another data source. A workflow keeps the data source it was created on, so create a new workflow on the other data source. See Create and edit a workflow. |
<name> is a system generated workflow and cannot be removed. | DataMind OS created this workflow, so it stays. |
<name> still has N transformation(s) assigned and cannot be removed. | Move the transformations to another workflow, then delete again. See Rearrange transformations. |
<name> still has N table(s) assigned and cannot be removed. | Move the tables to another workflow, then delete again. See Workflows in the Lake or Run, schedule and monitor Writeback. |
| No workflows found | Nothing matches the search, chips or filters. Clear them with Reset filters. |
| No matching sources | The search in Filters matches no data source. Change it. |
| No datasources found. | The search matches nothing, or you cannot add any data source type. Change the search, or ask for an Add permission. |
| Set up notification channels in Admin first (bell tooltip) | No channel is set up, or you cannot see notification channels. Add a channel under Admin > Notifications, see Notifications. |
| Workflow enabled successfully or Workflow disabled successfully | You turned the schedule on or off from the workflow's card or from a tab's menu. Nothing is wrong: On starts runs when the schedule allows, Off stops scheduled runs. See Schedules and when a workflow starts. |
| You see | What it means and what to do |
|---|---|
| Can’t run yet with "None of this workflow’s tables are deployed, so it has nothing to load into. Deploy at least one table, then run it." | Select Show datasource and deploy a table. See Configure a table. |
| Can’t run yet with "None of this workflow’s tables have finished column mapping, so it has nothing to push. Map at least one table, then run it." | Select Show destination and finish the column mapping of one table. See Map columns. |
| Run - deploy a table first (tab menu) | A table must be ready before this workflow can start: a deployed table for a Lake workflow, or a finished column mapping for a WriteBack workflow. Hover the card's Run to read the reason. See Run a workflow by hand. |
Unable to start <name>, at least one table must be deployed | Deploy a table first. |
The <name> cannot start, there is unfinished job(s) | A run is Running or Running Error. Wait for it, or stop it. See Monitor and fix a run. |
Data source "<code>" is being loaded by job <id> (<workflow>). | Another run is preparing or loading the same data source. Start again when that run ends. |
Data source "<name>" is still loading (<status>). | Wait until the data source is ready. |
| Flow scheduled successfully | The start was accepted and the run has begun. It does not mean the data has loaded yet; follow the new run's Status in the runs table until it shows Finished. |
| An unexpected error occurred (toast title Error) | The start failed with no reason from the server. Try again. |
| You see | What it means and what to do |
|---|---|
| Failed to load jobs | The runs table could not load. Select Refresh jobs, or reload the page. |
| Failed to load job timeline | The run timeline could not load. Reload the page. See System Trace and the run timeline. |
| Filter options failed with "Unknown error while loading filter options" | A column's filter list could not load, so it stays empty. Open the filter again to retry. See Job runs. |
| Failed to download jobs: invalid file response | The download did not return a file. Try the export again. See Job runs. |
| No jobs found | No run matches the filters. By default only full workflow runs show. Clear the filters, or select another workflow. See Job runs. |
| Failed to load nodes | The node window could not load. Close it and open the run again. |
| No nodes found | No step is visible. Turn on Show skipped nodes and Show system nodes, or clear the column filters. See Nodes in a run. |
| No job selected | The node window has no run to show. Open one from the runs table. See Job runs. |
| The job is running, please abort it before restarting. | Another run of this workflow is live. Stop it, then restart. See Monitor and fix a run. |
Data source "<code>" is being loaded by job <id> (<workflow>). | Restart when that run ends. |
| The Job is already in error state. | The run is already Aborted or Failed. There is nothing to stop. |
| Cannot delete with "You do not have permission to delete this job." | The delete is refused. When the text under the title reads this, you lack the Remove permission for the run's workflow type. Ask an administrator. See Workflow permissions. |
| Are you sure you want to restart this job? or Are you sure you want to stop this job? or Are you sure you want to delete this job? | The action asks for confirmation first. Confirm to continue: a restart runs only the nodes that did not finish, a stop aborts the run, and a delete removes it permanently. |
| Job restarted successfully, Job stopped successfully or Job deleted successfully | The action worked, and the run's state changed. Nothing is wrong. See Monitor and fix a run. |
| Failed to restart job, Failed to stop job or Failed to delete job (toast title Error) | The action failed. The text below the title is the server's reason when it sent one; otherwise it reads like this. Try again. |
| The job doesn't exist or The Job doesn't exist or the job doesn't exist | The run no longer exists, for example because it was deleted meanwhile. Refresh the runs table and open the run again. |
| Aborted by User (in Error Stack) | You stopped the run. Restart it, or run the workflow again. See Monitor and fix a run and Run logs and step messages. |
| Skipped due to previous node error (in Note) | An earlier node this one depends on failed. Fix that node, then restart the run. See Nodes in a run and Run logs and step messages. |
| Cross-workflow dependency not satisfied: followed by the table, its source system and the reason | A Gate failed. The reason after the message says what the gate found: the other run did not produce the table, or the wait ran out first. Fix the other workflow, run it again if needed, then restart this run. See Nodes in a run. |
| Gate not satisfied: (in Note) | A Gate was skipped, and the steps that waited on it were skipped too. The run does not fail for this reason. Fix or run the other workflow, then run this one again. See Nodes in a run and Run logs and step messages. |
| Proceeded on possibly stale data: followed by the reason | A Gate ran out of its wait and the run continued on data already loaded. Check that the data is fresh enough for the run's posting date. |
"<workflow>" is disabled and will not run; proceeding on its last loaded data | The other workflow's schedule is Off, so its Gate passed at once and the step reads the last loaded data. Turn that workflow's schedule on if this date needs fresh data. |
| Preparation cancelled: (in Note) | File preparation was cancelled from the data source. Run again when the files are ready. See Nodes in a run and Run logs and step messages. |
Table "<name>" not found or Transformation "<name>" not found | The table or transformation was deleted or renamed. See Monitor and fix a run. |
| Export failed with "Too many exports are running at the moment, try again shortly" | The export service is busy with other exports. Try again shortly. See Job runs. |
| Nothing to export with "No data to export." | No run is loaded for the current filters, so no file was built. Clear the filters or select another workflow, then download again. |
| You see | What it means and what to do |
|---|---|
| Full Reload From Date Not Reached | The Full Reload Start Date is after the date the run loaded for, so nothing was loaded yet. Set an earlier Full Reload Start Date so the load can start. |
Full reload from date <date> is after <date>; nothing to load yet or Full reload from date <date> is after posting date <date>; nothing to load yet | The same skip, written on the step itself during a first run. Set an earlier Full Reload Start Date. |
| Earliest Source Date Not Found | The search for the earliest date in the source did not answer, so the first run fell back to the set start date. Set Full Reload Start Date so the first run does not depend on the search. |
<n> (clamped from <m> to the earliest source date) | The first run's span was clamped to the earliest date the source has. Nothing is wrong; set Full Reload Start Date if you want a specific window. |
| 0 (the source has no dated rows) | The source returned no dates, so the first run covers no days of history. Check the source's data if you expected a start date. |
Rows of <n> other day(s) were loaded and are discarded: <days> | A reload of chosen days returned rows for days you did not ask for, and they are not loaded. Check the days you chose and the table's incremental column. |
<n> file(s) have no date in their name and are not loaded: <names> | Files whose names carry no date were left out of the load. Check the file names and the file group's date settings before loading again. |
| Skip Reason: One Time Table Already ran | A one-time load already ran and had rows, so the new load was skipped. Nothing is wrong; a one-time table loads once. |
Empty Staging Tables Failed with "Warning, the run itself succeeded: <reason>" | The run's own work finished; only the cleanup of the staging tables failed. Nothing is wrong; the run still succeeded. |
| Eligibility Warning Ignored | A run started by hand went past a warning-level eligibility check. Nothing is wrong; error-level checks still stop a run. |
| TransformationRefused: followed by the reason | The run stopped before sending any statement, because the query contains something the platform refuses. Edit the query as the reason says, then run again. |
| History is not eligible to run | The history step was skipped, and no more specific reason was recorded. Check the table's history settings and its load state. |
| unknown (the Processed Rows step of a history run) | The last insert returned no row summary, so no count was recorded. Nothing is wrong; a missing count is never a guess. |
The step messages and skip reasons are explained in full on Run logs and step messages.
| You see | What it means and what to do |
|---|---|
| Failed to save alerts | The changes were not saved. The text below the title is the reason when the server sent one. Saving channels needs a Modify workflow permission, and unticking a channel needs a Remove workflow permission. See Failure alerts. |
| No channels selected. Saving removes every alert for this workflow. | Every channel is unticked, so saving would delete all of this workflow's alert recipients. Tick the channels you want to keep, or continue through the Remove alerts confirmation to stop every alert. |
| This workflow will stop sending notifications to every channel. This action cannot be undone. | The Remove alerts confirmation. Confirm to stop every alert, or cancel and tick the channels you want to keep. |
| Pick at least one recipient (under the recipient list) | An Email channel has no recipients. Pick at least one person. |
| No channels configured. Add one in Admin first. | Add a channel under Admin > Notifications. See Notifications. |
| No alert notifications in this period | No alert message was recorded for this workflow in the chosen period. Widen the period, and if you expect messages, check that the workflow has alert recipients and that its channels are active under Admin > Notifications. |
| No alert recipients configured (a delivery log entry with status Skipped) | Nothing was sent for that failed run because the workflow has no alert recipients. Set up at least one channel for the workflow from the bell on its card. |
| This workflow no longer exists. | The workflow was deleted while its alerts window was open. Close the window. |
| You see | What it means and what to do |
|---|---|
| Workflow not available with "It may have been deleted, or you do not have access to it." | The workflow window cannot show this workflow. Check that it exists and that you have the View permission for its type. See Workflows in chat. |
| Workflows could not be loaded with "Close this window and open the workflow again." | Close the window and open the workflow again. |
| No Workflow Data with "Workflows will be displayed after at least one run." | The workflow has no runs yet, so the diagram has nothing to draw. Run the workflow once. See Run a workflow by hand. |
No nodes matching "<query>" | The node search found no visible step for your text. Check the spelling, or clear the search; the search covers visible transformation steps only. |
| No visible transformation nodes | There is nothing for the search to look at, for example because a filter or highlight hides every transformation step. Clear the filter or the highlight, then search again. |
No filters found matching "<query>" | The header filter has no option whose name matches your text. Clear the text; the options cover the table names, source systems and semantic sources that exist in the run. |
| Export successful or Workflow diagram has been exported as PNG | The PNG was built and downloaded. Nothing is wrong; find the file in your downloads, named workflow-{jobId}-{ISO date}.. |
| Export failed with Failed to export workflow diagram | The picture could not be exported. Try again, and leave the diagram alone while it works. See Workflow diagram. |
| Export cancelled with the error's message | The export stopped before it finished. Try it again; if it keeps stopping early, close other heavy windows first. |
| The diagram is too large for this browser to export | No canvas size the browser can allocate fits this diagram. Show less at once, with filters or a timeline moment, and export again. |
| Diagram export timed out | The export hit its time limit before the image was ready. Try again, and leave the diagram still while it works. |
| The diagram kept changing during export | The layout kept moving while the image was prepared. Leave the diagram alone during the export and try once more. |
| The diagram was closed or reloaded before the image was ready | The export was abandoned because the diagram went away. Keep the diagram open until the download appears, then export again. |
| Cannot update node without transformation ID (toast title Error) | The node has no transformation to switch on or off. |
| Cannot modify node: followed by the reasons No Transformation ID, View Only Mode or Workflow is Running | The schedule switch is locked, and the tooltip lists each blocking reason that applies. Choose Current Workflow and let the run end; a step with no transformation behind it keeps the lock. |
| Failed to update schedule (reason below the title) | Switching a node's schedule failed. The reason names the cause, for example a transformation on a dependency cycle. Switching needs Add/Modify Warehouse Objects. See Workflow diagram. |
| Failed to update node. Changes have been reverted. (toast title Error) | The schedule change was refused, and the switch went back. See Workflow diagram. |
| You see | What it means and what to do |
|---|---|
| Access denied. Required permission(s): followed by the permission names | You lack a permission for this action. The names after the message are the permissions that would allow it. Ask an administrator for them. See Workflow permissions. |
Access denied. | You hold this permission for another workflow type only. Ask for it for this type. |
| Access denied. You do not have permission to read this CoreTable | Opening a Warehouse run's diagram needs Warehouse object access on top of the workflow View permission. Ask an administrator for View Warehouse Objects or Add/Modify Warehouse Objects from the Data Layer category. |
A workflow that does not start on its schedule shows no message. Check these causes in order, and fix the first one that applies.
Work through the checklist in the section above, starting with the Workflow Scheduler. The first step that is not right is the cause. Details are on Schedules and when a workflow starts.
The server refused the values and sent no reason. The usual causes are a Batch Size above 100 or a name another workflow already uses. The field goes up to 1000, but the save accepts at most 100, so use 100 or less and a unique name. See Create and edit a workflow.
A message carries the server's own reason when the server sends one. When it does not, the message falls back to its generic text, such as Failed to restart job or An unexpected error occurred. The generic text means no reason was sent, not that one is hidden.
You lack the permission for that action, or you hold it only for another workflow type. The message names the permissions that would allow it. Ask an administrator for them. See Workflow permissions.
The field is empty. Type a number in it.
No run matches the current view. By default the table shows only full workflow runs, so table syncs, test runs and single transformation runs stay hidden until you filter Run Scope. Check the other column filters and the selected workflow too. See Job runs.
Open its nodes to see which step is still working or waiting. A Gate waits for a table another workflow should produce, for up to 60 minutes. If the run must end, stop it. See Monitor and fix a run and Nodes in a run.
Another run of the same workflow is live. Stop it, or wait until it finishes, then restart. See Monitor and fix a run.
No step is visible. Skipped steps and system steps are hidden by default, so turn on Show skipped nodes and Show system nodes, and clear the column filters. See Nodes in a run.