To resolve the issue of an empty currentBillingSubscription when calling verify, follow these steps:

1. Verify Billing Service Fetch Method: Ensure that getCurrentBillingSubscription in /packages/twenty-server/src/engine/modules/billing/billing.service.ts correctly queries for the current billing subscription based on the workspace ID and that it handles cases where a subscription might not exist.

2. Check Workspace Resolver: In /packages/twenty-server/src/core/workspace/workspace.resolver.ts, confirm that the resolver method which calls getCurrentBillingSubscription correctly passes the workspace ID and handles the response, especially null or undefined subscription cases.

3. Frontend Data Handling: In /packages/twenty-front/src/pages/settings/SettingsBilling.tsx, ensure that the component correctly handles and displays the state when currentBillingSubscription data is null or empty. This might involve adding conditional rendering logic to display a message or a default state when no subscription data is available.

4. Debugging and Logging: Add logging at critical points within the billing service and workspace resolver to trace the flow of data and identify where the breakdown occurs. This can help pinpoint if the issue is with data retrieval, data passing, or frontend display.

These steps target the specific components involved in the issue based on the provided codebase structure. Adjustments may be needed based on additional findings during the debugging process.

References

twentyhq/twenty/packages/twenty-server/src/core/workspace/workspace.resolver.ts
twentyhq/twenty/packages/twenty-server/src/engine/modules/billing/billing.service.ts
twentyhq/twenty/packages/twenty-front/src/pages/settings/SettingsBilling.tsx

Ask Greptile