CRON Import Node - GlobalAction
The CRON Import Node is available in GlobalAction only.
This node will need to be downloaded from the Square 9 SDN before proceeding.
The CRON Import node is a GlobalAction only node that begins processing based on a specified CRON expression. Once triggered, it imports documents into the workflow and continues processing them at set time intervals until no more documents are found, allowing controlled, gradual ingestion of data. This approach is ideal for handling large volumes without overwhelming the system, particularly for low-frequency or off-peak processing scenarios.
Cron Import Node
Node Properties
CRON Import Node Settings
Title
Add a title for this node. Your title should be brief but descriptive about what is being picked up. Titles are useful when reading the history in the history of a workflow for easier understanding of the overall process.
Description
Provide a synopsis of what this node is doing, or make note of any important details. Since this node uses ID’s, it’s a good idea to add specifics about the Database, Archive, and Search being used. A good description is helpful when returning to modify the workflow in the future.
Frequency
Includes settings for Days, Hours and Minutes. By default, this is set to 15 minutes. Setting the frequency is important for how often you’d like the next group of documents to be processed once the CRON expression is evaluated as TRUE.
The Data Validation checkbox is enabled by default to enforce Data Types or Length settings for Fields. When enabled, if data does not meet the type or length settings for the field, the process will error on this node.
Database ID
Each GlobalSearch database is given a unique Database ID in SQL. No two Databases will have the same Database ID.
Archive ID
Each Archive within a GlobalSearch database is given a unique Archive ID in SQL. No two Archives within the same Database will have the same Archive ID.
Search ID
Each Search created within an archive is given a unique Search ID in SQL. No two Searches within the same Database will have the same Search ID.
Getting Database, Archive, and Search ID’s
The easiest way to obtain the Database, Archive, and Search ID’s is from the URL. From the document viewer, run a search that will return the document to enter the workflow through the CRON import node.
GlobalSearch Go: https://www.square9.cloud/db/1012/archive/1/search/1
GlobalSearch Legacy Browser: https://educationtest.mysquare9.com/square9web/index.html#/results/2998dd6adf7e30d8e92fae2046f0892f61441804c0b5abbdae34735927c4f44b?Id=8&archive=2&db=1012&criteria=&time=1754074336025
Return Limit
Control the number of processes entering the workflow at the set frequency.
CRON Expression
The expression to evaluate. Once the CRON expression is evaluated as TRUE, documents will continue to be ingested into the workflow in groups indicated by the Return Limit at the rate indicated in the Frequency.
Generate
The Generate button takes you to a website that helps you write and test CRON expressions. If you have added an expression to the CRON Expression field, it will evaluate that expression for you and explain it in common language.
Note: Once the CRON expression is evaluated as TRUE, documents will continue to be ingested until no more are found.
Ex. If the Return Limit is set to 10, the Frequency is set to 30, and 25 documents are found when the CRON evaluates as TRUE, the first 10 documents will process, then 30 minutes later, the next 10 documents will process, finally, 30 minutes after that, the final 5 documents will process. The processing will then stop until the CRON evaluates at TRUE again.
CRON Expressions
A web search will return numerous quality results to better help you understand CRON expressions. We also recommend this one for building and understanding expressions.
A typical expression will be broken down into 5 positions separated by a space, in the form:
Minute | Hour | Day of Month | Month | Day of Week |
|---|---|---|---|---|
0-59 | 0-23 | 1-31 | 1-12 | 0-6 (Sunday - Saturday) |
Example Patterns:
Pattern | Result |
|---|---|
5 4 * * * | Execute at 4:05 AM every day |
1 * 1 1 * | Execute at the 1st minute of the first day of January, annually |
0 9 * * 5 | Execute every Friday at 9AM |
Use Case
Importing a fixed number of documents at a specific time.
In this example, the CRON Import node imports documents that residing in Database 1012, Archive 5, and are returned by Search 15. The search is executed at 10 PM every day (CRON expression 0 22 * * * ) and the process is limited to 10 document every 15 minutes.
At 10 PM each night, the search will be run and documents will be processed 10 at a time every 15 minutes until no more are found. The process will then be idle until 10 PM the next night.
If at 10 PM 32 documents are returned by the search, the first 10 will be ingested at 10 PM, the next 10 at 10:15 PM, the next 10 at 10:30 PM, and the last 2 at 10:45 PM. Since there are no longer any documents, the process will halt until 10 PM the next day.
