Start with the transfer whose result is missing or appears incorrect. Note the name or identifier of the data, the integration, the transfer direction and the approximate processing time. Use the log to find out what happened during processing; also verify the result in the relevant data in Spotilla and the other system.

Prerequisites and choosing the right log

Logs are viewed in the browser version of Spotilla with admin user permissions. The Android and iOS apps do not have these log views. Integration processing of data saved on mobile is also investigated in the browser.

Open Settings from the main menu and select Integrations. There are two different log views:

  • Shared log: open the Changelog tab.
  • Integration-specific log: open the LemonERP, Procountor (New), KIHO or GSFleet tab, then open Integration Logs within it. The integration's tab is only visible when that integration has been enabled for the organization.

These are separate logs: the same event may not appear in both. For LemonERP and Procountor connections in particular, check whether you are using the new connection with its own tab or the old integration configuration. If the connection you need is not visible, see prerequisites for enabling an integration.

Find the event in the shared Changelog

Select the period to search from the Log created at menu above the table. The default is Day, meaning the current day. Week searches a period starting seven days ago and ending today. 1 Month searches a period starting one month ago and ending today. These do not mean a calendar week or calendar month. Both boundary dates are included in the search.

When you select Filter by specific time range, set the start and end dates in the adjacent Date range field. The view may restore your previous filters, so always check them before interpreting the results.

Narrow down the retrieved data using the filters below the column headings: Timestamp, Software, Item type, Target, Status code and Description. Column filters do not extend the date range selected above. If the event falls outside that range, change the main filter first. Events are retrieved with the newest first by default.

Read Status code together with the Description column. The status code is a value recorded with the event; it is not the Status in the integration-specific log, and you should not assume that they have the same meanings.

Find the event in the integration's own log

Set the date range using the date filter below the Time column heading. Events on the selected start and end dates are included in the search. This log does not have the shared log's default filter for the current day, and the default order is newest first.

Refine the search using the text filters in the Job, Direction, Entity Type, Status and Message columns. You can also search using part of the text. Multiple filters narrow down the results together.

  • Job gives the name of the processing operation. It may appear as a technical name and does not necessarily mean a Spotilla task or work order.
  • Direction: inbound means importing from another system into Spotilla, and outbound means exporting from Spotilla to another system. The direction alone does not confirm that data was transferred.
  • Entity Type indicates the type of data or processing involved. A row may also summarize the entire run.
  • Item displays a name when a corresponding Spotilla record can be found for the log entry. An empty item alone does not indicate an error. The name is retrieved from the current record, so it may differ from the name at the time of the event.

The item name may open the related Spotilla record. Opening records is supported for customers, contacts, folders, offers, contracts and contract invoices. Not all entity types have a working link, even if the name looks like a link; if necessary, find the data in its own view.

Interpret the status and message together

  • ok: the operation described in the row succeeded. This may mean creating new data, updating data or simply linking existing data.
  • noop: processing was skipped or no change was needed. This does not guarantee that the data you intended to transfer was transferred.
  • error: an error was detected during processing. Check the message to see which operation and item it concerns.

Message explains what the row's status means in practice. For example, Bootstrap mapping created in a LemonERP customer import may appear with the status ok even though no new customer was created: an existing customer was linked. Missing cost center — skipped appears with the status noop and means that processing of a new customer was skipped because the cost center was missing.

A successful connection test in the log does not by itself prove that an invoice or other business data was transferred. Check the result of the specific operation and any other rows belonging to the same processing operation.

Verify the result and determine the next steps

Compare the log entry with the relevant data in Spotilla and the receiving system. For imports, the receiving system is Spotilla; for exports, it is the other system. Check whether the correct record exists, whether it is linked to the correct item and whether the expected fields have been updated.

If you cannot find a row, expand the date range, remove overly specific column filters and check that you are using the correct integration implementation and log. A missing log row alone does not prove that the transfer succeeded or failed: for example, saving the log may fail independently of the processing itself.

Reading, filtering or sorting the log does not retry the transfer or change the data being processed. If the message concerns authentication, check the correct environment and the connection's credential settings. If it concerns a missing field or mapping, correct its configuration before transferring again. Connection-specific instructions: LemonERP, Procountor, KIHO and GSFleet.

Do not start a large-scale retransfer because of a single unclear row. First check which data was processed successfully and what the retry would process. If necessary, provide support with the date range, integration name and log used, direction, item, status or status code, and message or description. Do not include passwords, API keys or other secret credentials.