@Sagar - I’ve successfully implemented a connector to NetSuite that uses OAuth2. After a period of about 7 days (didn’t measure precisely) the associated trigger fails to ever complete and ultimately locks the entire Tulip App. To resolve the issue I have to go into the connector definition and repeat the test process (reauthorizing through the NetSuite screens).
Is there any way to either:
- Recognize the authentication failure in the trigger and respond to it, or
- Automatically re-authenticate so no human intervention is required
The observed behavior is intolerable for a shop floor application and if this is a technical limitation I’ll have to consider how we rearchitect to avoid the use of connectors.