Updating an instance
Last updated
Last updated
Having added an instance, you can make changes to basic details and authentication details, at any time. If you update an instance that has already been used in process flows, your changes will be cascaded down to them automatically.
To update an existing instance for one of your installed connectors, follow the steps below.
Step 1 Log in to the Patchworks dashboard and select process flows > connectors & instances to access the manage connectors page.
Step 2 Find the required connector and instance.
If you can't find the connector here, it means the connector is not installed. In this case, navigate to the Patchworks marketplace and install the required connector.
Step 3 Click the 'cog' icon associated with the instance that you want to update - for example:
Step 4 The instance settings page is displayed - from here you can view/update instance details:
Available options are summarised below:
Step 5 Click the authentication tab to view/update authentication details:
If you update authentication fields, credentials are checked - only valid credentials can be saved.
Please see Adding an instance for more information about these fields.
Step 6 Click the save instance details button to confirm any changes:
| Option | Summary |
|---|---|
Name
The name for this instance to be applied throughout Patchworks.
Connection pool
If the connector associated with this instance has a concurrency limit and you have configured connection pools, these are available for selection here.
To remove a connection pool associated with an instance, click the 'cross' icon:
For more information see our Connection pools page.
Time zone
Used to convert the time in any date/time filters that are applied when this instance is used in process flows.
Date format
The expected date format when this instance is used in process flows.
Rate limit amount Rate limit unit
Determines the rate at which Patchworks is allowed to make API requests to the associated system when using this instance of the connector. If the rate limit for an instance is exceeded, remaining requests are queued and sent when the rate limit is released again.
Default settings are provided but you may need to adjust this to suit your specific needs. For example, you might have a plan which allows you a higher rate limit, or you might have multiple instances for the same connector running at the same time, which all need to share a rate limit. If you're not aware of any specific requirements, leave the default settings as they are.
