# Input Message
Defines input parameters to ingest data from a Timer Source.
This Asset is used within a Workflow definition.
You need: A Timer Source
# Name & Description
Name : Name of the Asset. Whitespaces are not allowed in the name.
Description : Enter a description.
Asset Usage box shows how many times this Asset is used and which parts are referencing it. Click to expand and then click to follow, if any.
# Output Ports
An input processor can only have one output port from which it sends ingested data downstream in the Workkflow.
A port can have a name and description. Names must exist and be unique within the processor.
# Termination Settings
Using termination settings you can control how layline.io should behave upon shutdown of a Workflow that this Asset is part of. A Workflow shutdown at most goes through three phases:
- Signalling shutdown: layline.io signals inputs that it wants to shut down.
- Signalling abort: In case the shutdown was not confirmed, layline.io sends an abort request.
- If the abort was not confirmed, layline.io terminates the input without further wait.
Shutdown grace period [ms]: Time to wait for the input processor to gracefully confirm shutdown once a shutdown request has been received.
Abort grace period [ms]: In case the shutdown signal was not confirmed in due time, an abort request will be issued. If the abort is not confirmed in the configured time interval, a hard termination will be issued. The abort timeout is consecutive to the shutdown timeout.
You need to assign a Timer Source. The Timer Source defines when a message is triggered and what the content of that message is.
# Failure Handling
Finally we have to define what should happen to the complete stream in case a problem is discovered. We have two options here:
# Rollback Stream
The complete stream processing will be rolled back, as much as this is possible. This includes, for example signals to rollback database actions (DB rollback event issued), as well as deletion of temporary files. Respective log messages will be generated to further analyze the cause of the issue.
# Retry Stream
When setting to
Retry Stream, the system will retry a failed action for a configured amount of times and in configured intervals.
Stream Retry Settings:
Max. Retries: Number of times a failed read action should be retried.
Min. backoff [ms]: The minimum number of milliseconds to wait in-between retries.
Max. backoff [ms]: The maximum number of milliseconds to wait in-between retries. This number must be equal or greater than the
Min. backoff [ms].
Let's assume we have set a min. backoff time of 60 seconds and a max backoff number 100 seconds with 3 retries. The system will then calculate three different timeouts ranging between 60 and 100 seconds. In our case that would be 60, 80 and 100 seconds. Or in other words, the system will wait for 60 seconds on the first retry, then 80 seconds between the first and second retry, and finally 100 seconds before the last retry. This allows us to delay retries with each retry. This is especially useful for problems which are related to failure in 3rd party interfaces (e.g. due to network issues), which experience show may be fixed only after a while. Let's say that there is a chance that a connection fails sometimes because of an unstable network. In that case we do not want to retry every second, but leave more time between each consecutive retry, until it finally works again (example).
# Related Topics
Can't find what you are looking for?
Please note, that the creation of the online documentation is Work-In-Progress. It is constantly being updated. Should you have questions or suggestions, please don't hesitate to contact us at firstname.lastname@example.org .