Microservice Frequently Asked Questions
This page answers common questions about Microservices.
What environment do Microservices run in?
TrackVia Microservices are executed as Amazon Web Service Lambda, configured with an x86 Node 16.x runtime or x86 Python 3.9 runtime.
Each microservice is provisioned with 1024 MB of memory.
What are the limitations of a Microservice?
-
Microservices are limited to a total runtime of 15 minutes.
-
Microservices do not have access to IAM or other AWS services.
-
Microservices packages (ZIP) may only be 40MB in size.
-
Microservices are standalone - there is no access to layers.
-
All microservices are subject to TrackVia’s Terms of Service and security policies.
Can an App Script trigger a Microservice?
No. An App Script does not trigger a Microservice.
A Microservice runs only when one of these record actions occurs:
- Create
- Update
- Delete
A record update can trigger a Microservice. A bulk update does not. This rule applies to a bulk update made through the UI and through the API.
The source of the change decides the result:
| Activity | Where it runs | Triggers a Microservice? |
|---|---|---|
| App Script | Inside the platform | No |
| API endpoint call | From an external client | Yes |
What is the default timeout for a Microservice?
15 minutes.
A Microservice can update a resource that runs a second Microservice. The second Microservice must complete before the first one can. Keep the number of chained Microservices small. To reduce the wait, set the Microservice to run asynchronously.
Can I run a Microservice on a schedule?
Yes. Use a Workato integration to invoke the Microservice on a schedule. Workato is TrackVia’s integrations platform. See Integration options and Workato’s Scheduler documentation .
Does a Microservice keep running when the browser loses its connection?
Yes. The platform triggers the Microservice after it saves the record to the database. From that point, the browser plays no part. The Microservice then runs synchronously or asynchronously, as its setup defines.
Can I fire Microservices in bulk?
Yes. Call the /invoke endpoint of the OpenAPI to run the Microservice. The
Microservice code can then do the bulk work, such as a bulk update. You can
call the endpoint at any time. See the /invoke endpoint in the
OpenAPI documentation.
What is the maximum file size for a Microservice upload?
The compressed archive (.zip) can be 40 MB at most.
What is the difference between GET and POST when I invoke a Microservice?
Both methods invoke the Microservice. A POST request can also carry key-value parameters in its body. The Microservice code can read those parameters. A GET request has no body, so it cannot carry parameters in the same way.
If a form has several fields that trigger Microservices, do they run in a set order?
No. The Microservices run in no set order.
Does a new sandbox get the production account’s Microservices?
No. A new sandbox does not get a copy of the Microservices. Upload each Microservice again in the sandbox. Then connect it to its table again.
If a Microservice calls the TrackVia API, change it to use the sandbox account
ID. For OpenAPI calls to a sandbox, use the API key and the auth token of the
parent account. Add an account-id header. Set it to the sandbox account ID.
The user behind the token must exist before the sandbox creation. That user
must also be a Super Admin before the sandbox creation. Only a Super Admin
can call the /invoke endpoint.
Can a Microservice trigger another Microservice?
Yes. A Microservice can make an API call that creates or updates records. That call can trigger downstream Microservices.
This chain can cause:
- recursive loops
- runaway automation
- duplicate processing
When should I use a Microservice instead of an App Script?
Use an App Script for:
- field validation
- calculations
- workflow logic
- record-level automation
- child record changes
Use a Microservice for:
- external integrations
- notifications
- third-party APIs
- asynchronous processing
- enterprise orchestration
What is the difference between App Scripts and Microservices?
| App Scripts | Microservices |
|---|---|
| Run inside TrackVia | Usually run from an integration or an event |
| Run synchronously during a transaction | Often run asynchronously |
| Best for record logic | Best for integrations |
| Limited to the platform runtime | Can connect to external systems |
| Do not trigger Microservices | Run when a qualifying event occurs |
Check out our getting started guides or read our FAQs for best practices and common questions to start extending your app!