Synatic uses flows to create integrations across data environments. These flows are made up of a series of steps that will define your data process. There are varying actions that can be employed, such as reading data from a source, filtering data, transforming to a particular format, calling other systems, writing data to a data source, or sending messages to a destination.
As in traditional programming, errors can be introduced in various ways during the development process or in the live runtime scenario. It is evident that such errors should be avoided at all times. This can be done using test points shown in the image below.
A recommended technique to limit the introduction of errors into Synatic flows is to develop cautiously and use the test points to test the flows often.
The articles below will discuss how errors or anomalies may be accidentally introduced into a flow, and how to use Synatic's test points to debug and resolve the errors.
Run Statuses
Processing – The run for the flow that is currently being processed.
Completed – All records that are successfully processed.
Completed with Errors – All records that are processed but contain errors.
Failed – All records that failed.
Stalled – The run did not process due to an issue with the data, flow or resources on the worker. Please contact support@synatic.com to investigate the cause of why the run has stalled.
Queued – the organization is stored on a shared worker which has a limited number of resources. When a run goes into a queued status, it means that the worker is currently processing a limited number of runs simultaneously. When a run from the processing set of runs on the worker is completed, it will then process the next run that is waiting in the queue on the worker.
Click an option below to view a relevant article: