Joule Setup / Error during Booster Execution

[LukasKuhn]

Hello Experts,
we have tried to integrate Joule with our TDD System using the End-to-End Setup Guide (Joule – End-to-End Setup Guide (for all Line of Bu... - SAP Community). For context the joule entitlement is in one subaccount and the workzone entitlements are in a different subaccount but under the same global account. Everything else was setup identical to the guide.

During the execution of the booster we encountered the following error:

or as text:
[SaaS Subscription/(module.joule_subscription.cis_saas_subscription.saas_subscription[0])] The subscription of subaccount (name of subaccount) to application das-application and plan foundation, failed with state: SUBSCRIBE_FAILED. - Error Message: 'Async callback of reuse service  'Document Grounding'  with appName document-grounding failed. It failed its asynchronous callback and responded with message: Service Document Grounding with appName document-grounding did not send its async callback response within the maximum allowed timeout of 300000 milliseconds. To resolve the issue, please contact this service's owner. (Root Application : Joule appName: das-application-ias. Please open support case using the component: CA-JOULE.)'. App Error: ''. 

Can anyone point us to what the issue might be and how to resolve it ?

Best regards 
Lukas

[George_Yu1]

Hi Lukas,

When you setup Joule for the Public Cloud, you work everything within one BTP sub-account. You will create one Joule and one Work Zone instance under the sub-account. When you have entitlements in two separate accounts, how can you put instances under one sub-account?

I haven't seen this error message before, seems quite complicated. Can you try to work everything under one sub-account first?

Regards,

George

[LukasKuhn]

Hi George, we had instances on the respective subaccounts. We also thought that this may be the cause of the error, so i changed it today and used one subaccount for joule and buildworkzone. Now the formation seems to have been created without errors. We still have some other errors but for now Joule is working.

[George_Yu1]

Hi Lukas,

Glad to hear it worked.

This whole Joule setup hinges around Trust or SSO setup, for example, you have to use the same IAS. Putting everything under the same sub-account at least makes life easier. 

Regards,

George

[LukasKuhn]

Hi @George_Yu1. I was wondering if you could help me with a different issue we currently face with Joule. Some of our users now can use Joule and some are missing the Diamond Icon entirely. While figuring out what the cause of this is, i noticed that one ContentChannel in our BuildWorkzone Instance is stuck on the status "in creation" for seven days (Screenshot 1) and that we are also missing a third tab in the settings for BuildWorkzone (Screenshot 2). Do you have any idea how we can fix this ?

In the End to End Setup Guide you have to check a box in this third tab, but its just missing in our instance of BuildWorkzone.

 

[Daphne_Mengwein]

Hi @LukasKuhn  I see that your original question could be solved. Please post a new question for any further topics. Thanks!