Fetching documents now

Fetch now checks the source for new documents straight away, outside the schedule. Use it to prove a new connector works or to pull in something urgent. The schedule carries on unchanged.

What you'll need

• The IntELIEKonnect app in your top bar.
• This permission: IntELIEKonnect · Import - Execute.
• An import connector that is Active, Connected and bound to something, such as an orchestrator's Import Channels.

If IntELIEKonnect isn't in your top bar, your role can't view it or your plan doesn't include it. Ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Find the connector

   Open Import Connectors, or open the connector itself.

   

   The Import Connectors list with the Fetch now cloud icon ringed in the row of Finance mailbox, an Active and Connected Email connector, and its tooltip: Check the source for new documents right now, without waiting for the next scheduled run.

   Enlarge

2. Select Fetch now

   Select Fetch now at the top of the connector, or its cloud icon in the row’s Actions. It reads Starting… for a moment, then _Fetch started_ confirms it. If every import worker is busy, a message says the fetch is queued instead, and it starts as soon as one is free.

3. Watch for documents

   The run happens in the background. New documents appear in the orchestrator the connector is bound to, usually within a minute or two. Select Refresh on its documents list to see them.

What success looks like

• Fetch started appears, or a message that the fetch is queued.
• New documents show up in the bound orchestrator, starting at Processing.

Why it might find nothing

A fetch only collects what the connector hasn't seen yet. Its first run counts from the moment you enabled it, so files already in the folder or mailbox before then are left alone, unless Import Existing Files (or emails, or records) was on before you enabled it. Filters on Configuration, such as a subject or a file type, also leave documents behind. An item is never imported twice, and one that can never be imported is skipped: see Handling skipped files.

Fetch now is hidden, not greyed out, unless the connector is Active and Connected, and your role can run it.

If something goes wrong

Symptom	Likely cause	What to do
No Fetch now anywhere.	The connector isn't Active and Connected, or your role lacks Execute.	See Enabling, disabling and removing.
A fetch is already in progress	A scheduled or earlier run is still going.	Wait for it to finish, then try again.
Couldn't start the fetch	Most often, the connector isn't bound to anything.	Bind it first. See Binding an import connector.
Fetch started, but nothing arrives.	Nothing new at the source, or the filters exclude it.	Check the filters on Configuration, and the source itself.

Next

• Binding an import connector to an orchestrator - where the documents go.
• Setting an import schedule - running it automatically.